bgpreport

Network · data from 2026-11-12

AS268521 PONTO.COM TELECOM

Registry name: AS268521 - PONTO.COM TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268521, 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.
45.162.148.0/22 No ROA Other IRR onlyRADB, TC 670 100% 67
2804:527c::/32 No ROA Other IRR onlyTC 634 100% 67

AS-SET

AS268521'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 13 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none45.162.148.0/22No ROA covers it. Add a ROA for AS268521, maxLength 22.670 of 673
Route object: RIR45.162.148.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:527c::/32No ROA covers it. Add a ROA for AS268521, maxLength 32.634 of 636
Route object: RIR2804:527c::/32Route object only in TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

45.162.148.0/24RADBNo ROA
45.162.149.0/24RADBNo ROA
45.162.150.0/24RADBNo ROA
45.162.151.0/24RADBNo ROA
142.95.0.0/16ALTDBNo ROA
192.197.229.0/24ALTDBNo ROA
204.225.153.0/24ALTDBNo ROA
205.210.172.0/22ALTDBNo ROA
205.233.194.0/24ALTDBNo 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.