Polygon (Mainnet) - Erigon EOL & Migration to Bor
Last updateresolvedSep 1 · 15:32 UTC
Maintenance ended
Reported by Tatum on their status page.

checked Sep 7, 2026 8:54 PM UTC · Tatum's official status page
Tatum is up and running.
All components operational
Statusfield watches Tatum alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
7 reports published by Tatum in the last 30 days · 1 still open
When Tatum breaks, it is typically resolved in 3h 40m — median across 20 resolved incidents over 90 days.
resolvedSep 1 · 15:32 UTC
Maintenance ended
Reported by Tatum on their status page.
resolvedSep 1 · 08:43 UTC
**[Resolved] Cronos Network Issue** The recent issue affecting the Cronos network has now been resolved. Please note that this incident was caused entirely by a third-party outage on the Cronos network side. [See the official announcement](https://x.com/CronosNetwork/status/2094295199346573593) From the moment it occurred, our team worked tirelessly to mitigate the impact of this external failure and restore service as quickly as possible. Current Status: **Network operations are fully restored.** Throughput may currently be limited. We are operating on a temporary fallback setup while our team actively works on fully restoring our primary node infrastructure to return performance to 100%. We appreciate your patience while we finalize the full restoration.
Reported by Tatum on their status page.
resolvedAug 24 · 13:00 UTC
The service has been reestablished
Reported by Tatum on their status page.
degradedAug 24 · 09:21 UTC
BSC (Mainnet) is experiencing a service degradation on US services. The team is investigating. We will provide an update as soon as we have more information we can share.
Reported by Tatum on their status page.
resolvedAug 20 · 17:00 UTC
Maintenance ended
Reported by Tatum on their status page.
resolvedAug 13 · 08:08 UTC
The service has recovered.
Reported by Tatum on their status page.
resolvedAug 12 · 10:43 UTC
The incident has been resolved. Response times have returned to baseline across methods.
Reported by Tatum on their status page.