bgpreport

Network · data from 2026-11-12

AS262311 IMBRANET TELECOM

Registry name: AS262311 - IMBRANET TELECOM, BR · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
0Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS262311, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS262311, 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.
177.124.0.0/21 Valid Other IRR onlyRADB, TC 671 100% 66
177.124.0.0/22 Valid Other IRR onlyRADB 670 100% 66
177.124.3.0/24 Valid Other IRR onlyRADB 670 100% 66
177.124.4.0/22 Valid Other IRR onlyRADB 670 100% 66
2804:d08::/32 Valid Other IRR onlyRADB, TC 635 100% 69
2804:d08::/33 Valid Other IRR onlyRADB 635 100% 69
2804:d08:8000::/33 Valid Other IRR onlyRADB 635 100% 69
177.124.0.0/23 Valid Other IRR onlyRADB 203 30% 54
177.124.2.0/23 Valid Other IRR onlyRADB 203 30% 54
177.124.4.0/23 Valid Other IRR onlyRADB 203 30% 54
177.124.6.0/23 Valid Other IRR onlyRADB 203 30% 54

AS-SET

AS262311'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 22 are in fix.csv.

  • Route object: RIR11
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
Route object: RIR177.124.0.0/21Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.124.0.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.124.3.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.124.4.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:d08::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:d08::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:d08:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR177.124.0.0/23Route object only in RADB. Add it in the RIR database for the space.203 of 673
Route object: RIR177.124.2.0/23Route object only in RADB. Add it in the RIR database for the space.203 of 673
Route object: RIR177.124.4.0/23Route object only in RADB. Add it in the RIR database for the space.203 of 673
Route object: RIR177.124.6.0/23Route object only in RADB. Add it in the RIR database for the space.203 of 673

Route objects not announced

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

177.124.0.0/24RADBValid
177.124.1.0/24RADBValid
177.124.2.0/24RADBValid
177.124.4.0/24RADBValid
177.124.5.0/24RADBValid
177.124.6.0/24RADBValid
177.124.7.0/24RADBValid
2804:d08::/34RADBValid
2804:d08:4000::/34RADBValid
2804:d08:8000::/34RADBValid
2804:d08:c000::/34RADBValid

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.