bgpreport

Network · data from 2026-11-12

AS19930 EQUINIX-EC-CH - Equinix, Inc.

Registry name: EQUINIX-EC-CH - Equinix, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19930, 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.

198.32.106.0/24 No ROA Other IRR onlyRADB 671 100% 67
198.180.156.0/24 No ROA Other IRR onlyRADB 671 100% 67
198.180.158.0/24 No ROA Other IRR onlyRADB 671 100% 67
2607:f6f0:203::/48 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS19930 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 28 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
ROA: none198.32.106.0/24No ROA covers it. Add a ROA for AS19930, maxLength 24.671 of 673
Route object: RIR198.32.106.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.180.156.0/24No ROA covers it. Add a ROA for AS19930, maxLength 24.671 of 673
Route object: RIR198.180.156.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.180.158.0/24No ROA covers it. Add a ROA for AS19930, maxLength 24.671 of 673
Route object: RIR198.180.158.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2607:f6f0:203::/48No ROA covers it. Add a ROA for AS19930, maxLength 48.636 of 636
Route object: RIR2607:f6f0:203::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

Route objects with origin AS19930 whose prefix no peer sees AS19930 announce. Many are kept on purpose (backup routes, space announced only in some places).

64.191.215.0/24RADBNo ROA
136.175.161.0/24ARINNo ROA
142.215.16.0/22RADBNo ROA
142.215.56.0/22RADBNo ROA
142.215.58.0/24RADBNo ROA
142.215.59.0/24RADBNo ROA
142.215.104.0/24RADBNo ROA
142.215.192.0/21RADBNo ROA
142.215.197.0/24RADBNo ROA
142.215.198.0/24RADBNo ROA
149.97.136.0/22RADBNo ROA
149.97.208.0/22RADBNo ROA
149.97.248.0/22RADBNo ROA
155.204.152.0/21RADBValid
155.204.152.0/22RADBValid
155.204.152.0/24RADBValid
216.247.114.0/24RADBNo ROA
216.247.115.0/24RADBNo ROA
2607:f6f0:203::/64RADBNo ROA
2607:f6f0:3000::/40RADBNo ROA

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.