Backbone.direct Back to website

Report a network issue

Tell us what’s affected so we can investigate.

All fields are required unless marked optional.

Affected service
BGP details
Issue details

Use your local time.

Include affected traffic or prefixes, whether it’s still happening, and any recent changes or checks you’ve made.

IP transit diagnostics

An IP is tested exactly as entered. For a subnet, we test the network address plus one (.1 for a /24, ::1 for a /64). /32 and /128 identify a single host. Enter a specific responding IP if the subnet’s first host is unused.

Run mtr -n -r -w -c 100 DESTINATION_IP from the affected connection, replacing DESTINATION_IP with a host in the affected subnet. Paste the complete output, even if every hop times out. On Windows, run WinMTR for at least 100 packets and copy the text output.

If you or the remote operator can run MTR at the destination, test back to your source IP. Both directions help us identify routing asymmetry.

When you send, we ask Globalping to ping the target from Amsterdam, Frankfurt and London and include the results in your report. This can take up to 30 seconds. The target IP and measurement results are public through Globalping; your contact details and pasted MTR are sent only to support. External pings supplement your MTR. An unanswered ping alone does not prove an outage.

Useful: BGP summary, affected prefixes, ping or MTR output with source and destination IPs.

Remove passwords, BGP authentication keys and other secrets.

Your contact details

Sent to support@backbone.direct

Your contact details and diagnostics are emailed to our support team to investigate this issue.