cdnjs Status
Real-time updates of cdnjs issues and outages
cdnjs status is Operational
Active Incidents
No active incidents
Recently Resolved Incidents
No recent incidents
cdnjs Outage Survival Guide
cdnjs Components
CDN Service (cdnjs.cloudflare.com)
API (api.cdnjs.com)
Auto-update bot (github.com/cdnjs)
Website (cdnjs.com)
GitHub (github.com/cdnjs)
cdnjs Alternatives
CacheFly CDN Delivery - Europe
Our MXP1 PoP is currently experiencing an outage. All traffic is being re-directed to the next nearest pop
NGENIX Russia: Siberian Federal District
Krasnoyarsk (OZ-KRS)
Billing
We are currently observing and working to resolve the following Billing issues:
Failed Plan Modifications: There are intermittent issues with subscription upgrades, downgrades, and cancellations. This may result in billing charges being applied without the subscription level being updated. In these cases you may contact Cloudflare Support.
Unpaid Invoices Preventing Plan Modifications: If you encounter an error message when attempting to modify your plan, the most common cause is an unpaid invoice. In these cases, check if you have an unpaid invoice before contacting Support.
Missing Invoices: Some unpaid invoices are not visible. These unpaid invoices will still prevent account modifications. In these cases you may contact Cloudflare Support.
Missing Pay Now Buttons: For each unpaid invoice there should be a corresponding “Pay Now” button. If that button is not there you can click on the payment link directly within the invoice.
Expired Payment Links: After 120 days the payment links will expire, so if you have no “Pay Now” button and the link within the invoice is expired, you will need to contact to Support
Duplicate Payments: You may notice multiple invoices and charges on your bank and PayPal statements that appear to be duplicates. In most cases these are valid, unique charges for previously unpaid months where we were unable to collect your payments. You should not contact support about these cases.
Due to ongoing billing issues, we are experiencing high demand—please avoid opening duplicate tickets and wait for our response.
Dashboard
We are currently investigating reports that in some cases updates to the OWASP Managed Ruleset settings are not accurately reflected in the Dashboard UI, though these changes are taking effect and are still visible via the API.
Cloudlets
We are investigating an issue with Clouldlets Application Load Balancing (ALB) related to activations. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community (https://community.akamai.com/customers/s/support), or Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.
Edge Delivery
We are investigating an emerging issue with Edge Delivery where end-users in Europe and the USA may experience performance degradation. We are actively investigating the issue and will provide another update within the next 60 minutes.
We will soon be posting more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications.
If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community (https://community.akamai.com/customers/s/support), or Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.
We encountered an issue with Edge delivery related to connectivity issues. We have implemented a fix for this issue as of 02:27 UTC on 21 November 2024. Based on current observations, the service is resuming normal operations. Customers and partners can view additional details about the incident by logging into https://community.akamai.com/customers/s/feed/0D54R0000B1dEsSSQU or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue. We will continue to monitor to ensure that the impact has been fully mitigated.
We are continuing to [work with our third-party service provider to] investigate this issue. [Customers and partners can find more details on the Akamai Community: <link>.] [We will provide an update within the next XX minutes.]