01Okta · Oct 1Okta Workflows event-hook triggers failed to execute on Oct 1
Okta's status page logged incident I-11620, "Service Disruption in Workflows," starting 6:17 AM PT (13:17 UTC) on Oct 1. Per the status page, some automated event-hook triggers were not executing as expected; it was categorized as a Service Disruption, audience Admin, across eight listed okta.com cells (1, 2, 3, 4, 6, 7, 9, 11).
The page shows status Resolved, last updated Oct 1 23:59 UTC. The visible update text gives no root cause and the duration field reads 0, so we cannot state an outage length.
For your on-call: check whether any Workflows-driven provisioning or event-hook automations ran around Oct 1 13:17 UTC and re-run any that silently skipped.
02Stripe · Sep 30Stripe Visa network-token authorizations dipped for 1h42m on Sep 30
Stripe reported lower authorization rates on Visa network token transactions between 00:42 and 02:24 UTC on Sep 30, caused by a network token processing issue. Stripe said eligible payments could continue using card-number fallback and that no customer action was required; the incident was marked resolved at 03:40 UTC.
Stripe's resolution note does not name a deeper root cause.
For your on-call: compare Visa approval rates for Sep 30 00:42–02:24 UTC against baseline, and confirm your retries do not double-charge on fallback.
03Stripe · Oct 1Stripe API errors recur: four elevated-error incidents in ten days
On Oct 1 Stripe saw a brief rise in HTTP 5XX processing errors from 02:24 to 02:27 UTC; the incident was open 02:38–03:02 UTC. Earlier API-related incidents in the same mirrored history: Sep 22 (19:13–22:19 UTC, Stripe said it identified the root cause), Sep 23 and Sep 27 (00:05–01:01 UTC).
Count basis: Stripe incident titles mentioning API errors, Sep 22 – Oct 1, 2026, from a third-party mirror of Stripe's status page. Each was resolved and none was rated above minor.
For your on-call: confirm Stripe client retries use idempotency keys and back off, since short 5xx bursts have repeated across ten days.
04AWS us-east-1 · Sep 21AWS us-east-1 EC2 launches failed for about an hour after a bad deployment
Older item, not from this week: per the AWS Health Dashboard text mirrored by AWSDown, new instance launches in US-EAST-1 saw increased error rates between 3:49 PM and 5:06 PM PDT on Sep 21. RunInstances, CreateFleet, ECS, Fargate and EMR launches were affected; existing instances were not.
AWS attributed it to a recent deployment to an EC2 launch-request subsystem, rolled back, with recovery signs at 4:44 PM. No newer us-east-1 incident appeared in the aggregator's list for Sep 29 – Oct 5.
For your on-call: confirm autoscaling and Fargate-dependent services tolerate launch failures, and keep warm capacity for deploy-window launch errors.
05Okta · Sep 15Okta Office 365 launch failures listed at 4,977 minutes in September
Older item: Okta incident I-11462 began 8:15 AM PT (15:15 UTC) Sep 15. Launching Outlook, Calendar and People from Okta Dashboard chiclets intermittently returned HTTP 401, across about 18 listed cells for admins and end users.
The status page lists status Resolved and a duration field of 4,977 (about 83 hours if minutes). Okta's visible text gives no root cause.
For your on-call: if staff launch Office 365 through Okta chiclets, check Sep 15 help-desk tickets and whether a direct-URL workaround is documented.