ixreport

CentralNic Anycast A

AS199330 · Centralnic key-systems rrproxy Centralnicgroup

CentralNic Ltd

5Exchanges
1On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
ContentType
NoPeering policy
4Using the route servers
3To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with CentralNic Anycast A? · Where should CentralNic Anycast A peer next? · Compare CentralNic Anycast A with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in CentralNic Anycast A's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-11-19 18:41 UTC.

Make the changes on CentralNic Anycast A's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in CentralNic Anycast A's PeeringDB record. Add one entry per connection with these values.

  1. Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil · PeeringDB 171From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:73:0:3:aa2:0:1
    IPv4 address in PeeringDB, not in the export185.1.8.92 185.1.8.93185.1.8.92
    Port speed differs2 × 100M10G
    • In the entry with IPv4 185.1.8.92: set IPv6 to 2001:7f8:73:0:3:aa2:0:1 (now empty); set Speed to 10000 (10G) (now 100).
    • The entry with IPv4 185.1.8.93, IPv6 – isn't in the export: delete it if that connection is gone.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If CentralNic Anycast A has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583Not on its IX-F export or website members list
    IPv4195.66.244.90
    IPv62001:7f8:4:2:0:3:aa2:1
    Speed1000 Mbps (1G)

Exchanges over time

0246Oct 3, 2026Nov 19, 20265
Show as a table
DateExchanges
Nov 19, 20265
Nov 18, 20265
Nov 17, 20265
Nov 16, 20265
Nov 15, 20265
Nov 14, 20265
Nov 13, 20265
Nov 12, 20265
Nov 11, 20265
Nov 10, 20265
Nov 9, 20265
Nov 8, 20265
Nov 7, 20265
Nov 6, 20265
Nov 5, 20265
Nov 4, 20265
Nov 3, 20265
Nov 2, 20265
Nov 1, 20265
Oct 31, 20265
Oct 30, 20265
Oct 29, 20265
Oct 28, 20265
Oct 27, 20265
Oct 26, 20265
Oct 25, 20265
Oct 24, 20265
Oct 23, 20265
Oct 22, 20265
Oct 21, 20266
Oct 20, 20266
Oct 19, 20265
Oct 18, 20266
Oct 17, 20266
Oct 16, 20266
Oct 15, 20266
Oct 14, 20266
Oct 13, 20266
Oct 12, 20266
Oct 11, 20265
Oct 10, 20266
Oct 9, 20266
Oct 8, 20266
Oct 7, 20266
Oct 6, 20266
Oct 5, 20266
Oct 4, 20266
Oct 3, 20266

Map

Where CentralNic Anycast A's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 3.2G, at the 4 of 5 exchanges with a speed in PeeringDB or the exchange's IX-F export.

British Virgin Islands BVIX Road Town, British Virgin Islands 206.71.15.15 2001:504:93:0:206:71:15:15 1G Yes PeeringDB
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil Not in PeeringDB
United Kingdom LINX Manchester Manchester, United Kingdom 195.66.244.90 2001:7f8:4:2:0:3:aa2:1 1G Yes PeeringDB only
Slovakia SIX.SK Bratislava, Slovakia 192.108.148.22 2001:7f8:2f::22 1G Yes Both
United Arab Emirates UAE-IX Dubai, United Arab Emirates 185.1.8.92
185.1.8.93
2 × 100M Down Both IPv6 not in PeeringDBIPv4 not in exportSpeed differs

Exchanges in its buildings that it isn't on (2)

These exchanges have a switch in a facility where CentralNic Anycast A lists itself in PeeringDB, but don't have CentralNic Anycast A as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

United Kingdom Kent Internet Exchange PointKent, United Kingdom 102 Custodian CDC Maidstone 1
United States Global Peer ExchangeWashington, United States 6 Level(3) London (Goswell Road)
Facilities (2)

The buildings CentralNic Anycast A lists in PeeringDB, and how many of the exchanges in each it's on.

United Kingdom Custodian CDC Maidstone 1Maidstone 0 of 1
United Kingdom Level(3) London (Goswell Road)London 0 of 1