Nomic Platform Outage History
7 incidents recorded over the last 365 days, 7 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 Nomic Platform Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 15, 2026 | Document processing services experiencing failuresIncident resolved. | 362h 14m | Resolved |
| Sep 12, 2026 | Users experiencing intermittent message sending failuresAssistant sessions are now working correctly again in all regions. | 15 min | Resolved |
| Aug 5, 2026 | Delays in indexingThe backlog of unprocessed indexing jobs has cleared for the two affected customers. | 24h 31m | Resolved |
| Aug 4, 2026 | Elevated error rates in PDF processingThe issue with PDF processing has been resolved. | 18h 48m | Resolved |
| Jul 16, 2026 | Elevated rate of Authentication errorsOur authentication provider has fixed the problem and all authentication requests are now succeeding. | -436 min | Resolved |
| Jul 15, 2026 | Backlog of agent session requestsAll backlogged work was cleared | -662 min | Resolved |
| Jun 4, 2026 | Indexing system outageThe indexing subsystem experienced an outage on 06-04-2026; the system has been restored. | 51 min | 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 Nomic Platform 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 Nomic Platform 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 Nomic Platform 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 Nomic Platform outage in this window ran 15d 2h, against a mean recovery of 3d 9h. If you depend on Nomic Platform 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.