API outage
Resolved
Cloudflare has now marked its incident as resolved, and we are confident that the cdnjs API is now operating as normal.
Jun 12, 6:20 PMResolved Jun 12, 9:42 PMCriticalAPI (api.cdnjs.com)
Status Provider
Home
/
Status
/
Service
Home
/
Status
/
Service
Free open-source CDN service for faster, easier library file loading.
Source
auto
Category
Cloud
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 41m ago
3
Components
0
Active incidents
0
Maintenance
100%
90d uptime
API outage
Jun 12, 6:20 PM
Normalized official status-page data for incidents, maintenance, components, and history.
100%
Known uptime
1 known history days
3
Components tracked
0 outage, 0 degraded
15
Incidents indexed
0 active right now
5
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
API (api.cdnjs.com)
Operational
CDN Service (cdnjs.cloudflare.com)
Operational
Website (cdnjs.com)
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
0
outage days
0
maintenance days
89
unknown days
Latest outages and degradations detected from the official status page.
Cloudflare has now marked its incident as resolved, and we are confident that the cdnjs API is now operating as normal.
At this time we believe the fix to restore file content and SRI hashes is working as expected.
This incident has been resolved.
The API service has now been restored.
We are confident that the API service and the website are both stable.
This incident has been resolved.
At this time we are confident that access to the CDN has been restored for all users of cdnjs.
We are confident at this time that we have resolved the errors seen with the website & API, both are now handling library requests correctly.
We are confident at this time that all cdnjs assets are now available on the CDN once again. Cloudflare is continuing to see good recovery on their incident as well: https://cfl.re/2VbxQ96
We are now confident the fix is working as expected. The cdnjs website and API are now showing libraries and their versions correctly.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
At this time we are confident the auto-update bot has caught up with the backlog of new library versions and is stable following the changes made, concluding the maintenance.
Uptimus tracks the official Cdnjs status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.cdnjs.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 3 of 3 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
CDN Service (cdnjs.cloudflare.com) The cdnjs.com CDN infrastructure by Cloudflare - https://cdnjs.com/libraries | Operational | Component | Not recorded |
API (api.cdnjs.com) The cdnjs.com API service - https://cdnjs.com/api | Operational | Component | Not recorded |
Website (cdnjs.com) The cdnjs.com website - https://cdnjs.com/ | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Cdnjs is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
