Fragment Outage History

Fragment is up right now

Pingoru has recorded 6 incidents for Fragment: 4 in the last 12 months and 0 in the last 90 days.

Source: status.fragment.dev

6incidents recorded
4last 12 months
0last 90 days
3 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Fragment in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202624 of 720 (1%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 508 (0%)

Incidents, newest first

Minor April 6, 2026 Increased latency and error on us-east-1 4h 26m Ledger writes, Ledger reads

Started Apr 06, 2026, 04:32 PM UTC· resolved Apr 06, 2026, 08:58 PM UTC

  1. investigating Apr 06, 2026, 04:32 PM UTC

    Reads and writes should resume as normal

  2. resolved Apr 06, 2026, 08:58 PM UTC

    Reads and writes should be succeeding as normal. Asynchronous balances may be slightly delayed but will continue to process without notice.

Read the full incident report →

Minor November 12, 2025 Elevated error rate in eu-west-1 43m

Started Nov 12, 2025, 12:39 AM UTC· resolved Nov 12, 2025, 01:23 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor November 4, 2025 Accounts list in dashboard flickering 23m

Started Nov 04, 2025, 04:30 PM UTC· resolved Nov 04, 2025, 04:54 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major October 20, 2025 We're still seeing elevated error rates in us-east-1 5h 21m

Started Oct 20, 2025, 02:31 PM UTC· resolved Oct 20, 2025, 07:53 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical October 20, 2025 API in us-east-1 is down due to AWS incident 2h 20m

Started Oct 20, 2025, 07:55 AM UTC· resolved Oct 20, 2025, 10:16 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →