bgpreport

Network · data from 2026-11-12

AS265300 Regional Telecom

Registry name: AS265300 - Rede Regional Telecom, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265300, 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.68.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
200.106.132.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
200.125.176.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
2804:2dbc::/32 Valid Other IRR onlyRADB, TC 632 99% 67
168.121.68.0/23 Valid Other IRR onlyRADB, TC 186 28% 51
168.121.70.0/23 Valid Other IRR onlyRADB, TC 186 28% 51
200.106.132.0/23 Valid Other IRR onlyRADB, TC 186 28% 51
200.106.134.0/23 Valid Other IRR onlyRADB, TC 186 28% 51
200.125.176.0/23 Valid Other IRR onlyRADB, TC 186 28% 51
200.125.178.0/23 Valid Other IRR onlyRADB, TC 186 28% 51
200.106.132.0/24 Valid Other IRR onlyRADB 3 0%low visibility 3
200.106.133.0/24 Valid Other IRR onlyRADB 3 0%low visibility 3
200.106.134.0/24 Valid Other IRR onlyRADB 3 0%low visibility 3
200.106.135.0/24 Valid Other IRR onlyRADB 3 0%low visibility 3
200.125.176.0/24 Valid Other IRR onlyRADB 3 0%low visibility 3
200.125.177.0/24 Valid Other IRR onlyRADB 3 0%low visibility 3
200.125.178.0/24 Valid Other IRR onlyRADB 3 0%low visibility 3
200.125.179.0/24 Valid Other IRR onlyRADB 3 0%low visibility 3
168.121.68.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
168.121.69.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
168.121.70.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
168.121.71.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
2804:2dbc:a400::/38 Valid Other IRR onlyRADB 2 0%low visibility 2
2804:2dbc:a800::/38 Valid Other IRR onlyRADB 2 0%low visibility 2
2804:2dbc:e000::/38 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS265300: AS265300. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS265300 isn't in the set, or no route object for AS265300 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS265300 in itNot covered
AS265300 A single AS number, not a set: AS265300 (this network), 25 route objects.

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

  • Route object: RIR25
ChangePrefix or setDetailFull-table peers
Route object: RIR168.121.68.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.106.132.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR200.125.176.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:2dbc::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR168.121.68.0/23Route object only in RADB, TC. Add it in the RIR database for the space.186 of 673
Route object: RIR168.121.70.0/23Route object only in RADB, TC. Add it in the RIR database for the space.186 of 673
Route object: RIR200.106.132.0/23Route object only in RADB, TC. Add it in the RIR database for the space.186 of 673
Route object: RIR200.106.134.0/23Route object only in RADB, TC. Add it in the RIR database for the space.186 of 673
Route object: RIR200.125.176.0/23Route object only in RADB, TC. Add it in the RIR database for the space.186 of 673
Route object: RIR200.125.178.0/23Route object only in RADB, TC. Add it in the RIR database for the space.186 of 673
Route object: RIR200.106.132.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR200.106.133.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR200.106.134.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR200.106.135.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR200.125.176.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR200.125.177.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR200.125.178.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR200.125.179.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR168.121.68.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR168.121.69.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR168.121.70.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR168.121.71.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR2804:2dbc:a400::/38Route object only in RADB. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:2dbc:a800::/38Route object only in RADB. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:2dbc:e000::/38Route object only in RADB. Add it in the RIR database for the space.2 of 636

Route objects not announced

Every route object with origin AS265300 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.