bgpreport

Network · data from 2026-11-12

AS262307 Amplas Net Provedor de Internet

Registry name: AS262307 - Amplas Net Provedor de Internet Ltda, BR · PeeringDB

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

Announced routes

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

138.99.232.0/22 No ROA Other IRR onlyALTDB, RADB 672 100% 67
177.87.192.0/21 No ROA Other IRR onlyALTDB, RADB 671 100% 67

AS-SET

AS262307's PeeringDB record names no 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 9 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none138.99.232.0/22No ROA covers it. Add a ROA for AS262307, maxLength 22.672 of 673
Route object: RIR138.99.232.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.87.192.0/21No ROA covers it. Add a ROA for AS262307, maxLength 21.671 of 673
Route object: RIR177.87.192.0/21Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

138.99.232.0/23ALTDBNo ROA
138.99.234.0/23ALTDB, RADBNo ROA
177.87.192.0/22ALTDBNo ROA
177.87.196.0/22ALTDB, RADBNo ROA
2804:79c::/32RADBNo 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.