bgpreport

Network · data from 2026-11-12

AS27330 EQUINIX-EC-AT - Equinix, Inc.

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

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

Announced routes

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

2607:f6f0:7002::/48 No ROA Nonecovered by 2607:f6f0:7000::/40 3 0%low visibility 3
2607:f6f0:7000:190::/126 No ROA Nonecovered by 2607:f6f0:7000::/40 1 0%low visibility 1
104.194.201.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 67
198.32.104.0/24 No ROA Other IRR onlyRADB 671 100% 67
2607:f6f0:208::/48 No ROA Other IRR onlyRADB 635 100% 67
104.143.85.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS27330 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 19 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2607:f6f0:7002::/48No ROA covers it. Add a ROA for AS27330, maxLength 48.3 of 636
Route object: none2607:f6f0:7002::/48No route object for it. A route object for 2607:f6f0:7000::/40 with origin AS27330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27330 in the RIR database for the space.3 of 636
ROA: none2607:f6f0:7000:190::/126No ROA covers it. Add a ROA for AS27330, maxLength 126.1 of 636
Route object: none2607:f6f0:7000:190::/126No route object for it. A route object for 2607:f6f0:7000::/40 with origin AS27330 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS27330 in the RIR database for the space.1 of 636
ROA: none104.194.201.0/24No ROA covers it. Add a ROA for AS27330, maxLength 24.671 of 673
Route object: RIR104.194.201.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.32.104.0/24No ROA covers it. Add a ROA for AS27330, maxLength 24.671 of 673
Route object: RIR198.32.104.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2607:f6f0:208::/48No ROA covers it. Add a ROA for AS27330, maxLength 48.635 of 636
Route object: RIR2607:f6f0:208::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none104.143.85.0/24No ROA covers it. Add a ROA for AS27330, maxLength 24.2 of 673
Route object: RIR104.143.85.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

66.151.118.0/24RADBNo ROA
142.215.224.0/22RADBNo ROA
142.215.226.0/24RADBNo ROA
149.97.132.0/22RADBNo ROA
149.97.236.0/22RADBNo ROA
2607:f6f0:208::/64RADBNo ROA
2607:f6f0:7000::/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.