AMS IX Outage History
55 incidents recorded over the last 365 days, 32 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 AMS IX Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 5, 2026 | [SM-255] Planned Maintenance on Customer PortalWe will be undergoing scheduled maintenance during this time. | 3h 0m | Scheduled |
| Nov 1, 2026 | [NCDNTS-53] Management Network and Firewall Inaccessibility IssueThis has been restored and remain stable, with no further issues observed. Please note that peering traffic was not impacted during the period. If you have any questions regarding this incident, please do not hesitate… | 35 min | Resolved |
| Oct 27, 2026 | [SM-250] Swap Back Customers To Primary PE stub-ixn-249The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Oct 21, 2026 | [SM-249] Public website @ https://www.ams-ix.net unavailable – Security MaintenanceThe security fix has been applied and verified. Monitoring is complete and all systems are operating normally. No action is required. Thank you for your patience and understanding. | 22h 39m | Resolved |
| Oct 21, 2026 | [NCDNTS-52] Connectivity issue for some customers after Planned Maintenance[SM-248]As no recurrence has been observed, we will proceed with closing this incident. If you have any questions regarding this incident, please do not hesitate to contact us through our normal support channels. | 8h 14m | Resolved |
| Oct 21, 2026 | [SM-248] Planned Maintenance - Reboot of FPC 0 stub-ixn-249Due to an unexpected technical issue, the reboot of Linecard 0 (primary PE) was unsuccessful. The affected circuits listed below will remain on the backup PE device. Once the linecard issue is resolved, we will advise… | 3h 0m | Scheduled |
| Oct 20, 2026 | [NCDNTS-51] Jira mail issue - unable to send outbound mailThe issue impacting outbound emails has been resolved. Email replies are being sent successfully. | 1h 2m | Resolved |
| Oct 18, 2026 | [NCDNTS-50] Brief interruption on edge-rdh-050We have been closely monitoring the switch, and we can confirm that performance has remained stable since the incident occurred. As a result, we are now marking this issue as resolved and officially closing the… | 8h 2m | Resolved |
| Oct 16, 2026 | [SM-246] Planned Maintenance on Customer PortalThe scheduled maintenance has been completed. | 63h 0m | Scheduled |
| Oct 14, 2026 | [NCDNTS-49] Management Network and Firewall Inaccessibility IssueThis has been restored and remain stable, with no further issues observed. Please note that peering traffic was not impacted during the period. If you have any questions regarding this incident, please do not hesitate… | 1h 43m | Resolved |
| Oct 2, 2026 | [NCDNTS-48]Investigating Issue affecting Customer Portal for EG-IXThe incident has been resolved. The issue was caused by an unexpected behavior following the latest release. The root cause has been identified, and a fix has been implemented. The service is now operating normally. | 18h 3m | Resolved |
| Oct 1, 2026 | [NCDNTS-47] Investigating Issue affecting Customer Portal for MNM-IXThis incident has been resolved. It was caused due to an unnoticed behavior after the last release which has been already fixed. | 19h 46m | Resolved |
| Sep 24, 2026 | [NCDNTS-46] pxc-dr1-173 is downWe identified that the management interface for one of our PXC units became unreachable. This does not affect production traffic or service availability, all customer-facing systems remain fully operational. Our team… | 1h 3m | Resolved |
| Sep 18, 2026 | [NCDNTS-45] Investigating Issue affecting Route Server 1Following actions taken by our engineers to restore the affected components, services have been fully recovered and are operating normally. The incident was caused by an unexpected power outage. Our engineers restored… | 19h 55m | Resolved |
| Sep 16, 2026 | [NCDNTS-44] Portal ams-ix.me is unavailableSalesforce update: The Salesforce Technology team has observed that instance stability and performance are now at expected levels and declared the incident resolved. More information about the incident is posted here… | 18h 14m | Resolved |
| Sep 14, 2026 | [SM-241] Planned Maintenance - pxc-eqx-154 replacementThe scheduled maintenance has been completed. | 6h 0m | Scheduled |
| Sep 14, 2026 | [NCDNTS-43] Customer Portal IssueAs no additional issues have been reported since the resolution, we consider the incident resolved and will proceed with closing the ticket. | 6h 39m | Resolved |
| Sep 10, 2026 | [NCDNTS-42] Loss of backbone connections of stub-glo-254 and stub-glo-354Following the recovery action performed by our engineers to resolve the partial outage that occurred between Sept. 11 00:07 and Sept. 11 00:32 CEST, BGP sessions and customer connections have remained stable, with no… | 5h 47m | Resolved |
| Sep 10, 2026 | [NCDNTS-41] pxc-eqx-154 photonic switch outage at Equinix AM1Following the recovery actions performed by our engineers, pxc-eqx-154 has remained stable and we have not observed any further recurrences. As a proactive step to improve long-term reliability, we plan to migrate… | 9h 5m | Resolved |
| Sep 9, 2026 | [SM-240] Planned Maintenance - Hardware upgrade of the Hypervisor host for Route Server 1The scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Sep 9, 2026 | [NCDNTS-40] pxc-eqx-154 photonic switch outage at Equinix AM1Photonic switch is stable and all affected connections have been restored since 9:12 AM CEST. If you have any questions regarding this incident, please do not hesitate to contact us through our normal support channels. | 1h 46m | Resolved |
| Aug 27, 2026 | [SM-240] Planned Maintenance - Hardware upgrade of the Hypervisor host for Route Server 1We would like to announce a scheduled maintenance activity on our Hypervisor hosting the VM of the Route Server 1. During this maintenance window, our Hypervisor in Egypt will be turned off, in order to allow the field… | 9 min | Resolved |
| Aug 26, 2026 | [SM-238] Planned Maintenance - Hardware upgrade of the Hypervisor host for Route Server 2The scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Aug 24, 2026 | [NCDNTS-39] Email communication issue, noc@eg-ix.com.egAfter contacting local partner issue seems to be resolved. Start time: Aug 23, 2026, 23:02 CEST End time: Aug 25, 2026, 09:35 CEST If you have any questions regarding this incident, please do not hesitate to contact us… | 18h 43m | Resolved |
| Aug 14, 2026 | [NCDNTS-38] Traffic statistics issueThe traffic statistics have been restored and remain stable, with no further issues observed since August 17 at 10:16 for any of the affected locations. Please note that peering traffic was not impacted during this… | 76h 54m | Resolved |
| Aug 11, 2026 | [SM-234] CW - AS28017 router decommissioningThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Aug 10, 2026 | [SM-235] HK - AS58516 router decommissioningThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Aug 6, 2026 | [SM-237] SmartDC (SMT) Edge Switch MigrationThe scheduled maintenance has been successfully completed | 8h 0m | Scheduled |
| Aug 4, 2026 | [SM-234] CW - AS28017 router decommissioningThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Aug 3, 2026 | [SM-232] Planned Maintenance - Hardware upgrade of the Hypervisor host for Route Server 2The scheduled maintenance has been completed. | 6h 0m | Scheduled |
| Aug 2, 2026 | [NCDNTS-37] IPv4 BGP sessions down with RS1 in AmsterdamAll IPv4 BGP sessions with RS1 in Amsterdam went down at approximately 12:30 CEST. IPv6 BGP sessions on RS1 were not affected. The issue was identified and resolved at 13:42 CEST and the IPv4 BGP sessions were… | 0 min | Resolved |
| Jul 28, 2026 | [SM-231] Planned Maintenance - Hardware upgrade of the Hypervisor host for Route Server 1The scheduled maintenance has been completed. | 6h 0m | Scheduled |
| Jul 23, 2026 | [SM-230] Planned Maintenance - Load balancing on stub-imo-358 line card 1The scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jul 17, 2026 | [NCDNTS-36] Unexpected crash of line card 3 on stub-ix9-351 at Sara (Digital Realty AMS9)We have monitored the line card, and it has been stable since the event. The vendor case is pending for that unexpected crash and reboot of fpc 3 at stub-ix9-351. Any further actions are needed, they will be… | 1h 55m | Resolved |
| Jul 16, 2026 | [SM-228] GRN and SMT Management MigrationWe would like to inform you that the scheduled maintenance on our management network has been successfully completed. | 8h 0m | Scheduled |
| Jul 13, 2026 | [SM-229] Schedule reboot of stub-imo-358 FPC1We would like to inform you that a reboot has been performed. However, the sensor is still reporting incorrect readings. As a precaution, the affected customers are currently running on the backup path. We will continue… | 4h 0m | Scheduled |
| Jul 10, 2026 | [NCDNTS-35] Edge switch edge-rab-010 isolated – Rabale, MumbaiFollowing the implementation of corrective actions, the backbone links have remained stable, with no further flapping or traffic impact observed. The incident was determined to have been caused by a major fiber optic… | 4h 20m | Resolved |
| Jul 8, 2026 | [NCDNTS-34] Edge switch edge-rab-010 isolated – Rabale, MumbaiFollowing corrective actions, the backbone links have remained stable with no further flaps or traffic impact. The issue was caused by multiple fibre cuts. | 23h 34m | Resolved |
| Jul 1, 2026 | [SM-227] Planned Maintenance - Route Servers UpgradeThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Jul 1, 2026 | [NCDNTS-33] BGP sessions issue on RS2 Kolkata.The Route Server 2 has been migrated to the VMC01 and BGP sessions have been restored at 02:02 IST. We have been monitoring the sessions and they have remained stable. The incident has been resolved. We are working on… | 7h 54m | Resolved |
| Jun 29, 2026 | [NCDNTS-32] Unexepected reboot of multiple Juniper line cards at NikhefOn 30 June 2026 at 01:39 multiple line cards on one of our Juniper MX chassis unexpectedly rebooted. Customer and backbone links on those line cards were affected. At ~01:55 we observed that the links had recovered and… | 0 min | Resolved |
| Jun 26, 2026 | [NCDNTS-31] Issue with traffic statsStatistics are stable, and no further issues have been observed since the restoration. The issue was caused by a change mistakenly performed on the primary statistics collector instead of the standby system. Please… | 28h 33m | Resolved |
| Jun 25, 2026 | [SM-225] Planned Maintenance - Physical re-seat of line card at NikhefThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jun 20, 2026 | [NCDNTS-30] Jira mail issue - unable to send outbound mailThe root cause of this incident was a certificate chain issue that affected outbound email delivery. Our initial investigation suggested the add-on service was responsible but we have since confirmed it was not the… | 20h 58m | Resolved |
| Jun 17, 2026 | [NCDNTS-29] MUM-IX BGP sessions issue on RS2We would like to inform you that the incident has been resolved and officially closed. BGP sessions with the route server have remained stable. | 3h 55m | Resolved |
| Jun 16, 2026 | [NCDNTS-28] edge-gpx-020.mum - Line card 6 failureWe would like to inform you that the incident has been resolved and officially closed. If you have any questions regarding this maintenance, please do not hesitate to reach out to us via our normal support channels. | 37h 30m | Resolved |
| Jun 15, 2026 | [SM-223] Software upgrade of server hosting AMS-IX web pageThe scheduled maintenance has been completed. | 3h 30m | Scheduled |
| Jun 3, 2026 | [NCDNTS-27] BGP sessions down with RS2 in HyderabadThe BGP sessions were affected while a firewall policy was being deployed to the route server, which caused the peering prefix to be blocked. The issue was identified and fixed, and the BGP sessions were… | 1h 27m | Resolved |
| May 20, 2026 | [SM-222] Software upgrade of server hosting AMS-IX web pageWe are done with the rollback and everything is back to normal. A new maintenance will be announced at a later date. Apologies for the inconvenience. If you have any questions regarding this maintenance, please do not… | 1h 35m | Scheduled |
| May 18, 2026 | [SM-221] Database Cluster UpgradeThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| May 11, 2026 | [SM-220] Scheduled reboot of stub-imo-258 FPC0The scheduled maintenance is now completed. We have concluded our post-maintenance observation period. All systems are performing optimally | 4h 0m | Scheduled |
| May 7, 2026 | [SM-219] Migration of AMS-IX web page to a new server clusterThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| May 3, 2026 | [NCDNTS-25] Unexpected crash of line card FPC 0 PIC 1 on stub-imo-258We would like to inform you that the incident has been resolved and officially closed. Additionally, we have opened a maintenance window to continue with the follow-up activities recommended by our vendor. You can… | 85h 29m | Resolved |
| May 3, 2026 | [NCDNTS-24] EG-IX - IPv6 BGP issues on RS2Dear Members/Customers, An internal investigation identified the root cause as a corrupt route server configuration file. We have taken actions to mitigate future occurrences. After extensive monitoring of the BGP… | 41h 49m | Resolved |
| May 2, 2026 | NCDNTS-23 Ticketing system is degraded.The issue impacting our ticketing system was resolved, and normal service was restored. We continued to monitor the system to ensure stability. | -3 min | 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 AMS IX 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 AMS IX 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 AMS IX 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 AMS IX outage in this window ran 3d 13h, against a mean recovery of 11h 59m. If you depend on AMS IX 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.