SheerID Outage History
12 incidents recorded over the last 365 days, 11 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 SheerID Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 29, 2026 | Verification forms and My.SheerID.com degraded performanceThe fix was live as of around 22:03 UTC. After a monitoring period, it is now considered resolved. | 20 min | Resolved |
| Oct 14, 2026 | Increased API latency - This is a continuation/recurrence of the issue resolved earlier today.This incident has been resolved. | 30 min | Resolved |
| Oct 14, 2026 | Increased API latencyThis incident has been resolved. | 1h 29m | Resolved |
| Aug 28, 2026 | Latency and Timeouts in API endpointsThis incident has been resolved. | 30 min | Resolved |
| Jul 21, 2026 | My.SheerID login issuesOur reporting and management service, my.sheerid.com, was unavailable for approximately 15 minutes. This also caused downtime with our manual doc review system. The problem was addressed, the system has returned to… | -47 min | Resolved |
| May 29, 2026 | Increased API latencyThis incident has been resolved. | 18 min | Resolved |
| May 8, 2026 | Increased API latencyA cloud service provider caused increased latency across verification services. While the services remained operational and verifications processed, some customers may have experienced longer-than-usual wait times. | -802 min | Resolved |
| Apr 13, 2026 | Increased API latencyThis incident has been resolved. | 3 min | Resolved |
| Feb 10, 2026 | System degradation: Document reviewThis incident has been resolved. | 1h 0m | Resolved |
| Jan 28, 2026 | API LatencyAPI Latency resolved. | 4h 21m | Resolved |
| Dec 18, 2025 | Increased API latencyReports of latency starting at ~4:00 PM UTC. A fix has been implemented and we're monitoring the results. | -281 min | Resolved |
| Dec 11, 2025 | Upcoming system maintenanceThe scheduled maintenance has been completed. | 5 min | Scheduled |
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 SheerID 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 SheerID 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 SheerID 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 SheerID outage in this window ran 4h 21m, against a mean recovery of 57 min. If you depend on SheerID 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.