Is Fibery down?
Last checked 6m agoNo incidents right now.
Fibery is operational right now. Last checked 6m ago; the most recent incident resolved 49d ago.
Real-time Fibery status, recent outages, and incident history: pulled directly from Fibery's official status page at status.fibery.io every 5 minutes. Pingoru tracks 19 Fibery services and has captured 3 incidents in the last 90 days (99.88% uptime). Get email, Slack, Discord, or webhook alerts the moment Fibery reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 3 updates
- investigating · Sep 02, 2026, 06:00 PM UTC
We are investigating delays in notification delivery. Some users may not receive notifications in a timely manner..
- monitoring · Sep 02, 2026, 06:39 PM UTC
We implemented a fix and are currently monitoring the result..
- resolved · Sep 02, 2026, 07:03 PM UTC
This incident has been resolved..
Latest: This incident has been resolved..
-
-
Timeline · 2 updates
- investigating · Sep 02, 2026, 07:05 AM UTC
We are currently investigating this incident..
- resolved · Sep 02, 2026, 09:00 AM UTC
This incident has been resolved. We experienced elevated database load, which caused degraded performance for all users. We identified the issue as a combination of background formula processing and API client activity, and took steps to mitigate the load. Performance has since returned to normal..
Latest: This incident has been resolved. We experienced elevated database load, which caused degraded performance for all users. We identified the issue as a combination of background form…
-
-
Timeline · 2 updates
- identified · Aug 25, 2026, 08:01 AM UTC
We are seeing elevated error rates and slow responses for workspaces in the EU region due to increased database load. US and UK regions are not affected..
- resolved · Aug 25, 2026, 08:10 AM UTC
Error rates returned to normal at 08:10 UTC. Root cause: an internal background maintenance job coinciding with a spike in write activity overloaded the database. We have reconfigured the maintenance job and deployed an index fix to prevent recurrence..
Latest: Error rates returned to normal at 08:10 UTC. Root cause: an internal background maintenance job coinciding with a spike in write activity overloaded the database. We have reconfigu…
-
- Notifications ResolvedStarted Sep 02, 2026, 06:00 PM UTC · Resolved Sep 02, 2026, 07:03 PM UTC · 1h 2m
- Degraded performance ResolvedStarted Sep 02, 2026, 07:05 AM UTC · Resolved Sep 02, 2026, 09:00 AM UTC · 1h 55m
- Degraded performance in EU region ResolvedStarted Aug 25, 2026, 08:01 AM UTC · Resolved Aug 25, 2026, 08:10 AM UTC · 9m