bgpreport

Network · data from 2026-11-12

AS12600 EQUINIX-UKMS Equinix (EMEA) Acquisition Enterprises B.V.

Registry name: EQUINIX-UKMS Equinix (EMEA) Acquisition Enterprises B.V., NL · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 0.0% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
0No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS12600, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS12600, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
213.52.193.0/24 Invalid: origin None 127 19% 45
2001:4d78:145::/48 Invalid: origin None 103 16% 43

AS-SET

AS12600 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 4 are in fix.csv.

  • ROA: origin2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin213.52.193.0/24ROAs covering it name AS15830, not AS12600. If AS12600 should announce it, add a ROA for AS12600.127 of 673
Route object: none213.52.193.0/24No route object for it. Add a route object with origin AS12600 in the RIR database for the space.127 of 673
ROA: origin2001:4d78:145::/48ROAs covering it name AS15830, not AS12600. If AS12600 should announce it, add a ROA for AS12600.103 of 636
Route object: none2001:4d78:145::/48No route object for it. Add a route object with origin AS12600 in the RIR database for the space.103 of 636

Route objects not announced

Every route object with origin AS12600 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.