bgpreport

Network · data from 2026-11-12

AS265261 AS265261 - Tely Banda Larga

Registry name: AS265261 - Tely Banda Larga, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265261, 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.
2804:2d18:200::/40 Valid Nonecovered by 2804:2d18::/32 633 100% 67
168.0.232.0/22 Valid Other IRR onlyRADB 670 100% 67
2804:2d18::/32 Valid Other IRR onlyRADB 633 100% 67
168.0.233.0/24 Valid Other IRR onlyRADB 209 31% 56
168.0.235.0/24 Valid Other IRR onlyRADB 209 31% 56
168.0.232.0/24 Valid Other IRR onlyRADB 207 31% 56
168.0.234.0/24 Valid Other IRR onlyRADB 207 31% 56

AS-SET

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

  • Route object: none1
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none2804:2d18:200::/40No route object for it. A route object for 2804:2d18::/32 with origin AS265261 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265261 in the RIR database for the space.633 of 636
Route object: RIR168.0.232.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:2d18::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR168.0.233.0/24Route object only in RADB. Add it in the RIR database for the space.209 of 673
Route object: RIR168.0.235.0/24Route object only in RADB. Add it in the RIR database for the space.209 of 673
Route object: RIR168.0.232.0/24Route object only in RADB. Add it in the RIR database for the space.207 of 673
Route object: RIR168.0.234.0/24Route object only in RADB. Add it in the RIR database for the space.207 of 673

Route objects not announced

Every route object with origin AS265261 is announced.

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.