bgpreport

Network · data from 2026-11-12

AS262317 ROS Telecom

Registry name: AS262317 - ROS Telecom, BR · PeeringDB

30IPv4 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
4Route objects not announced registered with origin AS262317, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS262317, 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.91.122.0/23 Valid Other IRR onlyRADB, TC 667 99% 66
177.91.124.0/23 Valid Other IRR onlyRADB, TC 667 99% 66
177.91.126.0/23 Valid Other IRR onlyRADB, TC 667 99% 66
177.124.64.0/23 Valid Other IRR onlyRADB, TC 667 99% 66
177.124.66.0/23 Valid Other IRR onlyRADB, TC 667 99% 66
177.124.68.0/23 Valid Other IRR onlyRADB, TC 667 99% 66
177.91.120.0/21 Valid Other IRR onlyRADB, TC 666 99% 66
177.91.120.0/22 Valid Other IRR onlyRADB, TC 666 99% 66
177.91.120.0/23 Valid Other IRR onlyRADB, TC 666 99% 66
177.91.124.0/22 Valid Other IRR onlyRADB, TC 666 99% 66
177.124.64.0/21 Valid Other IRR onlyRADB, TC 666 99% 66
177.124.64.0/22 Valid Other IRR onlyRADB, TC 666 99% 66
177.124.68.0/22 Valid Other IRR onlyRADB, TC 666 99% 66
177.124.70.0/23 Valid Other IRR onlyRADB, TC 666 99% 66
2804:bac::/32 Valid Other IRR onlyRADB, TC 630 99% 69
177.91.120.0/24 Valid Other IRR onlyTC 135 20% 45
177.91.121.0/24 Valid Other IRR onlyTC 135 20% 45
177.91.122.0/24 Valid Other IRR onlyTC 135 20% 45
177.91.123.0/24 Valid Other IRR onlyTC 135 20% 45
177.91.124.0/24 Valid Other IRR onlyTC 135 20% 45
177.91.125.0/24 Valid Other IRR onlyTC 135 20% 45
177.91.126.0/24 Valid Other IRR onlyTC 135 20% 45
177.91.127.0/24 Valid Other IRR onlyTC 135 20% 45
177.124.64.0/24 Valid Other IRR onlyTC 135 20% 45
177.124.65.0/24 Valid Other IRR onlyTC 135 20% 45
177.124.66.0/24 Valid Other IRR onlyTC 135 20% 45
177.124.67.0/24 Valid Other IRR onlyTC 135 20% 45
177.124.68.0/24 Valid Other IRR onlyTC 135 20% 45
177.124.69.0/24 Valid Other IRR onlyTC 135 20% 45
177.124.71.0/24 Valid Other IRR onlyTC 135 20% 45
177.124.70.0/24 Valid Other IRR onlyTC 134 20% 45
2804:bac::/33 Valid Other IRR onlyTC 119 19% 44
2804:bac:8000::/33 Valid Other IRR onlyTC 119 19% 44

AS-SET

PeeringDB's irr_as_set for AS262317: AS262317. 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 (AS262317 isn't in the set, or no route object for AS262317 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 objectsAS262317 in itNot covered
AS262317 A single AS number, not a set: AS262317 (this network), 37 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 37 are in fix.csv.

  • Route object: RIR33
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR177.91.122.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR177.91.124.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR177.91.126.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR177.124.64.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR177.124.66.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR177.124.68.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR177.91.120.0/21Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR177.91.120.0/22Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR177.91.120.0/23Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR177.91.124.0/22Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR177.124.64.0/21Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR177.124.64.0/22Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR177.124.68.0/22Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR177.124.70.0/23Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:bac::/32Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR177.91.120.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.91.121.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.91.122.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.91.123.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.91.124.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.91.125.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.91.126.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.91.127.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.124.64.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.124.65.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.124.66.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.124.67.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.124.68.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.124.69.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.124.71.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.124.70.0/24Route object only in TC. Add it in the RIR database for the space.134 of 673
Route object: RIR2804:bac::/33Route object only in TC. Add it in the RIR database for the space.119 of 636
Route object: RIR2804:bac:8000::/33Route object only in TC. Add it in the RIR database for the space.119 of 636

Route objects not announced

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

2804:bac::/34TCValid
2804:bac:4000::/34TCValid
2804:bac:8000::/34TCValid
2804:bac:c000::/34TCValid

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.