Singpass Outage History
2 incidents recorded over the last 365 days, 2 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 Singpass Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 20, 2026 | Singpass Login is down | 380h 17m | Resolved |
| Jul 14, 2026 | [Staging] Singpass Login is down | 1890h 9m | 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 Singpass 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 Singpass 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 Singpass 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 Singpass outage in this window ran 78d 18h, against a mean recovery of 47d 7h. If you depend on Singpass 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.