No impact incident
Marathon: This is an example incident
Sep 27, 2026, 01:43 UTC
started
01:59 UTC
resolved September 26, 2026
—
duration
Current status of Marathon: Operational — live Marathon status
Timeline
- Sep 26, 2026, 01:49 UTCmonitoringLet your users know once a fix is in place, and keep communication clear and precise.
- Sep 26, 2026, 01:55 UTCidentifiedAs you continue to work through the incident, update your customers frequently.
- Sep 26, 2026, 01:59 UTCresolvedEmpathize with those affected and let them know everything is operating as normal.
- Sep 26, 2026, 02:25 UTCinvestigatingWhen your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.
Updates as published by Marathon (original).
Other services with incidents at the same time
- Snowflake 02:15 UTC · INC20000239
- Front 01:49 UTC · [us-west-2] Elevated API error rates may cause delays
- Render 01:24 UTC · Observing service instability from our upstream provider AWS in Oregon region
- Sumo Logic 01:22 UTC · Problem with Tracing Collection in North America 2 (US2)
- Crossref 01:22 UTC · Test admin tool - test.crossref.org - is down
- Olo 01:09 UTC · Payment Processor Issues: Stripe
- Figma 01:04 UTC · Service disruption
- Worldpay 01:03 UTC · INC0666335 - We are aware of potential issues with a third-party issuer behind the Mastercard Debit network.
- Stripe 01:03 UTC · Elevated API Errors
- npm 00:50 UTC · Issues with npm package publish and private install
- Olo 00:48 UTC · Dispatch Service Disruption: DoorDash
- LiveRamp External 00:44 UTC · Incident Resolved for Analytics Environment (EU) - Reporting (EU) via Grafana