bgpreport

Network · data from 2026-11-12

AS29884 EQUINIX-EC-DA - Equinix, Inc.

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

2IPv4 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
3No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
21Route objects not announced registered with origin AS29884, seen from no peer

Announced routes

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

142.215.106.0/24 No ROA Other IRR onlyRADB 670 100% 67
198.32.109.0/24 No ROA Other IRR onlyRADB 670 100% 67
2607:f6f0:204::/48 No ROA Other IRR onlyRADB 635 100% 67

AS-SET

AS29884 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 27 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: none142.215.106.0/24No ROA covers it. Add a ROA for AS29884, maxLength 24.670 of 673
Route object: RIR142.215.106.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none198.32.109.0/24No ROA covers it. Add a ROA for AS29884, maxLength 24.670 of 673
Route object: RIR198.32.109.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2607:f6f0:204::/48No ROA covers it. Add a ROA for AS29884, maxLength 48.635 of 636
Route object: RIR2607:f6f0:204::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

64.191.214.0/24RADBNo ROA
142.215.36.0/22RADBNo ROA
142.215.48.0/22RADBNo ROA
142.215.50.0/24RADBNo ROA
142.215.105.0/24RADBNo ROA
142.215.126.0/24RADBNo ROA
142.215.228.0/22RADBNo ROA
142.215.230.0/24RADBNo ROA
142.215.254.0/23RADBNo ROA
149.97.140.0/22RADBNo ROA
149.97.172.0/22RADBNo ROA
149.97.204.0/22RADBNo ROA
149.97.252.0/22RADBNo ROA
155.204.144.0/21RADBValid
155.204.148.0/24RADBValid
155.204.149.0/24RADBValid
198.205.101.0/24RADBNo ROA
2607:f6f0:204::/64RADBNo ROA
2607:f6f0:4000::/40RADBNo ROA
2607:f6f0:c000::/40RADBNo ROA
2607:f6f0:c100::/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.