Ports Group Outage History
Ports Group is up right nowPingoru has recorded 5 incidents for Ports Group: 1 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 3 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 515 (0%) |
Incidents, newest first
Major August 28, 2026 CNAME Flattening Service Disruption 2h 27m DNS Unicast Network, DNS Anycast Network
Started Aug 28, 2026, 11:40 AM UTC· resolved Aug 28, 2026, 02:07 PM UTC
- investigating Aug 28, 2026, 11:40 AM UTC
We are currently experiencing an issue with our CNAME flattening service, which is temporarily unavailable. This may affect DNS resolution for domains relying on this feature. Our engineering team is working on a solution, and we will post updates here as soon as we have more information. We apologize for any inconvenience this may cause.
- investigating Aug 28, 2026, 11:41 AM UTC
We are continuing to investigate this issue.
- monitoring Aug 28, 2026, 12:28 PM UTC
We've identified the root cause of the disruption. An internal fault caused two of our system components to become stuck waiting on each other, which prevented the lookups needed for CNAME flattening from completing. As a result, affected zones were mistakenly republished without the expected address records, causing resolution failures. Our team has resolved the underlying fault and is now republishing the affected zones with the correct records. We expect all zones to be fully operational within the hour. We will post a final update once service is confirmed fully restored.
- resolved Aug 28, 2026, 02:07 PM UTC
The underlying issue has been fixed, and all affected DNS zones have been correctly republished. CNAME flattening is now functioning normally. In some cases, resolvers may have cached the earlier incorrect (empty) result. Where this happened, it can take a little longer for the correct records to reappear. How long depends on the negative caching settings configured for that specific zone, but this should resolve on its own without any action needed. We apologize for the disruption this caused and thank you for your patience.
Critical June 12, 2025 Issue with Abion Core 5h 22m Abion Core
Started Jun 12, 2025, 08:08 AM UTC· resolved Jun 12, 2025, 01:30 PM UTC
- investigating Jun 12, 2025, 08:08 AM UTC
We are currently experiencing issues with Abion Core. The problem is identified and work is ongoing to solve it.
- investigating Jun 12, 2025, 10:16 AM UTC
Remedial action to restore services is still being undertaken with an estimated resolution time of 1315 CET
- monitoring Jun 12, 2025, 11:17 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 12, 2025, 01:30 PM UTC
This incident has been resolved.
Critical May 13, 2025 Network connectivity issues 36m
Started May 13, 2025, 09:55 AM UTC· resolved May 13, 2025, 10:31 AM UTC
- investigating May 13, 2025, 09:55 AM UTC
We are currently experiencing connectivity issues. This outage is affecting all on-prem services.
- investigating May 13, 2025, 10:09 AM UTC
Network connectivity has returned to normal. We're investigating root cause.
- monitoring May 13, 2025, 10:09 AM UTC
Upstream provider confirmed no issues on their end. Investigation continues.
- resolved May 13, 2025, 10:31 AM UTC
The incident is resolved
Major February 18, 2025 Network Outage –
Started Feb 18, 2025, 03:00 PM UTC· resolved Feb 18, 2025, 03:00 PM UTC
- resolved Feb 19, 2025, 04:06 PM UTC
Summary At approximately 15:46, our network experienced an outage due to an issue with our firewalls, which disrupted internet connectivity for all services hosted in our Gothenburg data center. The issue has now been resolved, with connectivity fully restored at 17:10. Systems Affected: - Web hosting - VPS hosting - VPN - Redirect services - Email services Customer Impact: Customers experienced an inability to access hosted websites, VPS, and any services dependent on our internet connection during the outage. Duration: The incident lasted approximately 1 hour and 21 minutes. Timeline 15:46: Network outage. 15:49: Connectivity issues were detected by our engineers. 15:55: Engineers were dispatched to the data center. 17:10: Connectivity restored. 17:10: Onward: Post-incident monitoring was initiated to verify full recovery. Resolution: The firewalls are fully functional again. Post-incident monitoring has confirmed that services are now operating normally. Our team is conducting a thorough review of the incident to prevent similar occurrences in the future. We apologize for any inconvenience this incident may have caused and appreciate your patience as we worked to resolve it.