Inter.link status page
  • Status
  • Events
  • Monitors
Get in touch
Inter.link
Inter.link Service Status
Jul 1, 2026
16 days ago
Network Outage – Point of Presence BUH1-RO (Bucharest, Romania)
Resolved · July 2 at 3:20 PM (UTC) (in 1 day)

Dear Customers,

We've been working with the fiber operator who have confirmed that the service instability was mainly due to an attenuation event on the the Bucharest–Sofia route.

The second path (Bucharest–Vienna) is fully diverse and was not directly impacted by the attenuation event, but it was already running with reduced OSNR margins because of a noisy amplifier.

The combination of the two issues caused the observed service flaps. The exact cause of the attenuation remains undetermined, and the amplifier will be replaced in an upcoming maintenance window. Furthermore, we're working with the provider to improve the escalation process for a faster resolution of any issues should they come up in the future.

Once again, we are sorry for any inconvenience this may have caused and we appreciate your understanding.

Investigating · July 1 at 3:05 PM (UTC) (1 day earlier)

Dear Customer,

We are still investigating the past service outage affecting our BUH1-RO Point of Presence (PoP) in Bucharest, Romania.

As of now, we haven't received a preliminary RFO. Escalations are in progress.

Based on our current findings, the service disruption occurred on July 1st, 06:57 am CET and lasted for a minute. Services have since been restored.

Our own findings lead to the assumption that our fiber operator must've had an outage at 2 separate paths.

We will share the RFO and any additional findings as soon as they become available.

We sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding.

Investigating · July 1 at 10:16 AM (UTC) (5 hours earlier)

We are currently investigating a brief outage that affected our Point of Presence BUH1-RO in Bucharest, Romania. The disruption occurred at approximately 06:57 CET and lasted up to one minute.

Customers connected to or routed through this PoP may have experienced an interruption during this window. Our team is actively working to identify the root cause and will provide further updates shortly.

Jun 26, 2026
21 days ago
Outage – PoP BUH1-RO (Bucharest, Romania)
Resolved · June 29 at 11:55 AM (UTC) (in 3 days)

The situation has remained stable as the acute incident has been resolved.

A preliminary statement from the service operator indicated two separate incidents that were not correlated with each other. One fiber-cut occurred 3.2 km away from Brașov, and the other occurred within the Bucharest NX data centre.

Monitoring · June 26 at 10:08 AM (UTC) (3 days earlier)

The cause of the issue has been identified.

Two separate services connecting our site BUH1-RO experienced service outages, overlapping during 07:54 UTC and 08:10 UTC. That led to a full outage to and from that site.

1 of 2 services is fully back online since 08:15 UTC and has remained stable since then. The other service is affected by an outage which results in degraded redundancy for now. We are monitoring the situation and will provide an update as soon as the status changes.

We remain in contact with the service operators and will share the RFO as soon as it is available.

Investigating · June 26 at 8:13 AM (UTC) (2 hours earlier)

We are currently investigating an active outage affecting our Point of Presence BUH1-RO in Bucharest, Romania. This issue may impact all customers connected, or routed through this PoP. Our team is actively working to identify the root cause and will provide further updates shortly

Jun 17, 2026
29 days ago
Service Disruption – POP SKG1-GR (Thessaloniki, Greece)
Resolved · June 18 at 1:00 AM (UTC) (in 2 hours)

Investigation confirmed that multiple concurrent fiber cuts in different regions caused a temporary loss of connectivity to our SKG1-GR PoP.

Repair work has been completed and all services have been fully restored as of 2026-06-18 01:45:45 UTC. We sincerely apologize to all affected customers for the disruption this caused.

Investigating · June 17 at 11:04 PM (UTC) (2 hours earlier)

We are currently aware of a service disruption affecting our POP SKG1-GR located in Thessaloniki, Greece. All customers connected via this POP are impacted. Our team is actively working with our suppliers to resolve the issue as quickly as possible. We apologize for the inconvenience and will provide updates as new information becomes available.

Jun 13, 2026
1 month ago
Core Backbone Outage — Bucharest to Vienna
Resolved · June 15 at 7:44 AM (UTC) (in 2 days)

The root cause of this incident has been identified. Our provider performed significant power adjustments on the Bucharest route to compensate for attenuation. Although the Bucharest–Vienna circuit does not run on that segment, the wavelength adjustment caused it to flap briefly, triggering the outage. No further action is required — the circuit has been stable since restoration at 15:20 UTC, and the integrity of redundancy on this route is not at risk.

Monitoring · June 13 at 3:49 PM (UTC) (2 days earlier)

Between 15:16 UTC and 15:20 UTC, customers experienced a brief service outage due to connectivity disruptions on the backbone link between Bucharest and Vienna. Redundant backup paths were simultaneously affected, resulting in a temporary traffic interruption. Full service was restored within 4 minutes. We are actively working with our third-party infrastructure partners to investigate the cause of the simultaneous path instability and ensure future redundancy resilience.

Jun 12, 2026
1 month ago
Fibre Cut — Sofia to Budapest
Resolved · June 16 at 1:39 PM (UTC) (in 4 days)

After monitoring the situation following the repair of the fibre cut between Sofia and Budapest, we can confirm that the path is operating normally. This incident is now resolved. We apologise for any inconvenience caused.

Monitoring · June 14 at 12:21 AM (UTC) (3 days earlier)

The fibre cut on the route between Sofia and Budapest has been confirmed as repaired as of June 14th, 00:21 UTC. Connectivity has been restored and we are currently monitoring the link for stability. We will provide a final update once we are confident in the stability of the route.

Investigating · June 12 at 12:14 PM (UTC) (2 days earlier)

We are currently experiencing network disruptions caused by a fibre cut on the route between Sofia and Budapest. Our team is actively working with our upstream provider to restore connectivity as quickly as possible. We will provide further updates as they become available.

Jun 11, 2026
1 month ago
Network Issue at Thessaloniki, Greece
Resolved · June 16 at 1:19 PM (UTC) (in 5 days)

Field team have performed repairs for multiple days and our redundancy is completely restored now. No further outages are expected at the PoP.

Monitoring · June 11 at 1:35 PM (UTC) (5 days earlier)

Field team have performed repairs and services have restored since 2026-06-11 11:18 UTC. Team are still working on site and not yet hands off. More updates will follow.

Identified · June 11 at 10:57 AM (UTC) (3 hours earlier)

We are currently investigating a service disruption affecting our Thessaloniki, Greece PoP. Our upstream provider is investigating a major fiber issue near the PoP Further updates will be provided as soon as additional information becomes available.

May 26, 2026
2 months ago
Network Issue at Balkan Gate, Thessaloniki
Resolved · May 26 at 2:28 PM (UTC) (in 4 hours)

Our provider has confirmed the restoration of the circuits. All services should now be stable again.

Monitoring · May 26 at 10:39 AM (UTC) (4 hours earlier)

The issue appears to be temporarily resolved, but we are still waiting for final confirmation from our provider and continue to monitor the situation closely.

Identified · May 26 at 10:23 AM (UTC) (17 minutes earlier)

Our provider has confirmed a fiber cut in the area, and restoration work is still ongoing.

Identified · May 26 at 10:13 AM (UTC) (9 minutes earlier)

We are currently investigating a network issue affecting Thessaloniki. The PoP is currently isolated/offline. Our provider is already investigating and working on the issue.

May 13, 2026
2 months ago
Network Issue at London Internet Exchange (LINX)
Resolved · May 15 at 11:35 AM (UTC) (in 2 days)

LINX have implemented the fix on their device and confirmed the network issue has been resolved.

All route servers sessions have been undrained.

Identified · May 13 at 2:09 PM (UTC) (2 days earlier)

We were informed about an isolated network issue, identified by and at the London Internet Exchange (LINX).

To mitigate potential impact, we have drained all route-server sessions at this location while preparing a maintenance at LINX to have them implement their suggested fix.

Traffic is automatically rerouting via redundant paths.

May 4, 2026
2 months ago
Network Issue at London Internet Exchange (LINX)
Resolved · May 11 at 3:13 PM (UTC) (in 7 days)

As the issue has been identified and solved by LINX and the sessions to the route-servers have been undrained, this incident is resolved.

Identified · May 11 at 6:59 AM (UTC) (8 hours earlier)

The support team of LINX has identified the root cause of the network issues we've identified so far. According to the most recent update, the root cause has been identified, the issue is fixed, and measures have been taken to prevent it from happening again.

As we can confirm the stability for now, we will go ahead and undrain our route-server sessions to make use of the best possible paths.

Investigating · May 8 at 10:57 AM (UTC) (3 days earlier)

Investigation with LINX remains ongoing. LINX is working to identify the issue and testing is underway.

After our initial action of draining the route-server sessions, no current issues are expected and traffic will use redundant paths for the time being.

Investigating · May 6 at 9:15 AM (UTC) (2 days earlier)

Investigation with LINX remain ongoing. After our initial action of draining the route-server sessions, no current issues are expected and traffic will use redundant paths for the time being.

Investigating · May 4 at 9:13 AM (UTC) (2 days earlier)

We are currently investigating a network issue affecting our presence at the London Internet Exchange (LINX). As a precautionary measure, we have temporarily drained all route-server sessions at this location to minimize impact while we work with our upstream supplier on a resolution. Traffic is being automatically rerouted via redundant network paths to maintain service continuity.

Apr 28, 2026
3 months ago
Network Issue - LINX, London (GB)
Resolved · April 30 at 10:17 AM (UTC) (in 2 days)

We have successfully implemented a permanent fix in coordination with our supplier. After a period of monitoring, we have confirmed the stability of the connection and are now re-enabling all route-server sessions at the London Internet Exchange (LINX).

Traffic will begin normalizing across these paths immediately. We will continue to keep a close watch on performance to ensure ongoing stability.

Identified · April 29 at 12:05 PM (UTC) (22 hours earlier)

Our supplier has identified the issue and a temporary fix is now in place. We have confirmed there is no impact to customer traffic, as all data continues to flow via redundant paths. We are monitoring the stability of the connection before restoring route-server sessions.

Investigating · April 28 at 12:55 PM (UTC) (23 hours earlier)

We are investigating a network issue at the London Internet Exchange (LINX). To mitigate impact, we have drained all route-server sessions at this location while we work with our supplier on a resolution. Traffic is automatically rerouting via redundant paths.

Apr 15, 2026
3 months ago
Network Link Congestion Between DUS1-DE and AMS1-NL
Resolved · April 15 at 9:14 PM (UTC)

We observed an overutilized link between our sites DUS1-DE and AMS1-NL between 21:00 and 21:43 CET today. Traffic engineering was performed at 21:41 CET to reroute traffic through our backbone network, mitigating potential impact from partial packet loss. The situation is now under control and link utilization has returned to normal conditions.

Mar 23, 2026
4 months ago
Investigating Impact of DDoS Attack
Resolved · March 23 at 10:33 PM (UTC) (in 14 hours)

Network status has returned to normal. All systems are operating as expected. If you continue to experience any issues, please contact our support desk.

Identified · March 23 at 10:30 PM (UTC) (3 minutes earlier)

We have identified the full scope of the incident. Due to the size and geographic distribution of the attack, traffic across multiple network ingress points saturated port capacities, resulting in impact to customer traffic. Attacks of this scale are rare occurrences. Inter.link continuously upgrades network capacity and DDoS countermeasures to mitigate such threats. All customer support tickets have been responded to. If you have any questions, please contact our support desk.

Investigating · March 23 at 8:19 AM (UTC) (14 hours earlier)

Yesterday between approximately 21:33 CET and 22:03 CET, our infrastructure experienced a massive DDoS attack targeting one of our customers. While the attack has been mitigated, our operations team is currently investigating the potential impact this incident may have had on other customers. We are committed to transparency and will provide an update on our findings later today.

Mar 19, 2026
4 months ago
Network Issue in Ashburn (US) via Equinix IXP
Resolved · March 19 at 8:30 AM (UTC)

We are currently investigating a network issue affecting traffic through the Equinix Ashburn IXP. At this time, we do not believe there is any impact on customer traffic. However, if required, we may temporarily disable access to the IXP to resolve the issue. During this time, customers in the US may experience slightly elevated latencies. We will provide updates as we learn more.

powered by openstatus.dev