GBIF Outage History
8 incidents recorded over the last 365 days, 4 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded GBIF Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 2, 2026 | Download complexity limitedThis incident has been resolved. | 43h 2m | Resolved |
| Oct 5, 2026 | Unplanned maintenanceThis incident has been resolved. | 5h 5m | Resolved |
| Sep 1, 2026 | Dataset crawling and indexing pausedScheduled maintenance is currently in progress. We will provide updates as necessary. | 84h 0m | Scheduled |
| Jul 17, 2026 | Taxonomy reprocessingThe scheduled maintenance has been completed. | 93h 0m | Scheduled |
| Jun 17, 2026 | Dataset crawling and ingestion suspendedThis incident has been resolved. | 17h 39m | Resolved |
| Jun 11, 2026 | Dataset crawling and ingestion pausing for launch of new GBIF.orgThe scheduled maintenance has been completed. | 168h 0m | Scheduled |
| Apr 23, 2026 | Planned outage in data crawling (23–30 April)The scheduled maintenance has been completed. | 171h 0m | Scheduled |
| Jan 26, 2026 | Disruptions due to power outageThis incident has been resolved. | 22h 37m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next GBIF incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This GBIF Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before GBIF acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single GBIF outage in this window ran 7d 3h, against a mean recovery of 3d 3h. If you depend on GBIF in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.