bgpreport

Network · data from 2026-11-12

AS265323 AS265323 - SPEEDMAX PROVEDOR LTDA

Registry name: AS265323 - SPEEDMAX PROVEDOR LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265323, 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.
168.121.204.0/22 No ROA Other IRR onlyRADB, TC 671 100% 66
168.121.204.0/23 No ROA Other IRR onlyTC 671 100% 66
168.121.205.0/24 No ROA Other IRR onlyRADB, TC 670 100% 67
168.121.206.0/23 No ROA Other IRR onlyTC 668 99% 66
2804:2e18::/32 No ROA Other IRR onlyRADB, TC 636 100% 69
2804:2e18::/33 No ROA Other IRR onlyTC 636 100% 69

AS-SET

AS265323 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 16 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none168.121.204.0/22No ROA covers it. Add a ROA for AS265323, maxLength 22.671 of 673
Route object: RIR168.121.204.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none168.121.204.0/23No ROA covers it. Add a ROA for AS265323, maxLength 23.671 of 673
Route object: RIR168.121.204.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none168.121.205.0/24No ROA covers it. Add a ROA for AS265323, maxLength 24.670 of 673
Route object: RIR168.121.205.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none168.121.206.0/23No ROA covers it. Add a ROA for AS265323, maxLength 23.668 of 673
Route object: RIR168.121.206.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:2e18::/32No ROA covers it. Add a ROA for AS265323, maxLength 32.636 of 636
Route object: RIR2804:2e18::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:2e18::/33No ROA covers it. Add a ROA for AS265323, maxLength 33.636 of 636
Route object: RIR2804:2e18::/33Route object only in TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

168.121.204.0/24RADB, TCNo ROA
168.121.206.0/24TCNo ROA
168.121.207.0/24RADB, TCNo ROA
2804:2e18:8000::/33TCNo 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.