bgpreport

Network · data from 2026-11-12

AS16397 AS16397 - EQUINIX BRASIL

Registry name: AS16397 - EQUINIX BRASIL, BR · not in PeeringDB

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

Announced routes

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

177.184.29.88/29 No ROA None 1 0%low visibility 1
5.62.51.0/24 Valid Other origin only 670 100% 67

AS-SET

AS16397 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 23 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
ROA: none177.184.29.88/29No ROA covers it. Add a ROA for AS16397, maxLength 29.1 of 673
Route object: none177.184.29.88/29No route object for it. Add a route object with origin AS16397 in the RIR database for the space.1 of 673
Route object: none5.62.51.0/24Route objects for it name AS198605. Add a route object with origin AS16397 in the RIR database for the space.670 of 673

Route objects not announced

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

142.215.101.0/24RADBNo ROA
159.242.224.0/23RIPENo ROA
177.47.0.0/19RADBNo ROA
177.126.160.0/19RADBNo ROA
177.154.128.0/19RADBNo ROA
179.124.32.0/20RADBNo ROA
187.33.8.0/22RADBNo ROA
187.33.12.0/23RADBNo ROA
187.33.20.0/23RADBNo ROA
200.143.160.0/19RADBNo ROA
200.155.0.0/20RADBNo ROA
200.155.64.0/20RADBNo ROA
200.198.176.0/20RADBNo ROA
200.219.192.0/19RADBNo ROA
200.219.224.0/19RADBNo ROA
201.20.0.0/19RADBNo ROA
201.20.32.0/20RADBNo ROA
201.20.48.0/20RADBNo ROA
201.150.92.0/22RADBNo ROA
2001:12e8::/32ALTDB, RADBNo 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.