cdnjs Outage History
1 incident recorded over the last 365 days, 1 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 cdnjs Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 30, 2026 | Searching libraries unavailableWe have confirmed that searching libraries on cdnjs continues to be available. Our upstream search provider has also confirmed resolution on their end. | 5h 6m | 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 cdnjs 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 cdnjs 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 cdnjs 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 cdnjs outage in this window ran 5h 6m, against a mean recovery of 5h 6m. If you depend on cdnjs 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.