bgpreport

Network · data from 2026-11-12

AS265166 SuperNetwork Telecom

Registry name: AS265166 - SuperNetwork Telecom, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265166, 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.
167.249.24.0/23 No ROA Nonecovered by 167.249.24.0/22 671 100% 67
167.249.24.0/24 No ROA Nonecovered by 167.249.24.0/22 3 0%low visibility 3
167.249.25.0/24 No ROA Nonecovered by 167.249.24.0/22 3 0%low visibility 3
167.249.26.0/24 No ROA Nonecovered by 167.249.24.0/22 3 0%low visibility 3
167.249.26.0/23 No ROA Nonecovered by 167.249.24.0/22 1 0%low visibility 1
167.249.27.0/24 No ROA Nonecovered by 167.249.24.0/22 1 0%low visibility 1
167.249.24.0/22 No ROA Other IRR onlyRADB 672 100% 67
2804:2ba4::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS265166: RADB::AS-265166. 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 (AS265166 isn't in the set, or no route object for AS265166 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 objectsAS265166 in itNot covered
RADB::AS-265166 In no IRR database read today.

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

  • ROA: none8
  • Route object: none6
  • Route object: RIR2
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none167.249.24.0/23No ROA covers it. Add a ROA for AS265166, maxLength 23.671 of 673
Route object: none167.249.24.0/23No route object for it. A route object for 167.249.24.0/22 with origin AS265166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265166 in the RIR database for the space.671 of 673
ROA: none167.249.24.0/24No ROA covers it. Add a ROA for AS265166, maxLength 24.3 of 673
Route object: none167.249.24.0/24No route object for it. A route object for 167.249.24.0/22 with origin AS265166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265166 in the RIR database for the space.3 of 673
ROA: none167.249.25.0/24No ROA covers it. Add a ROA for AS265166, maxLength 24.3 of 673
Route object: none167.249.25.0/24No route object for it. A route object for 167.249.24.0/22 with origin AS265166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265166 in the RIR database for the space.3 of 673
ROA: none167.249.26.0/24No ROA covers it. Add a ROA for AS265166, maxLength 24.3 of 673
Route object: none167.249.26.0/24No route object for it. A route object for 167.249.24.0/22 with origin AS265166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265166 in the RIR database for the space.3 of 673
ROA: none167.249.26.0/23No ROA covers it. Add a ROA for AS265166, maxLength 23.1 of 673
Route object: none167.249.26.0/23No route object for it. A route object for 167.249.24.0/22 with origin AS265166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265166 in the RIR database for the space.1 of 673
ROA: none167.249.27.0/24No ROA covers it. Add a ROA for AS265166, maxLength 24.1 of 673
Route object: none167.249.27.0/24No route object for it. A route object for 167.249.24.0/22 with origin AS265166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265166 in the RIR database for the space.1 of 673
ROA: none167.249.24.0/22No ROA covers it. Add a ROA for AS265166, maxLength 22.672 of 673
Route object: RIR167.249.24.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:2ba4::/32No ROA covers it. Add a ROA for AS265166, maxLength 32.636 of 636
Route object: RIR2804:2ba4::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
AS-SET: not foundRADB::AS-265166PeeringDB names RADB::AS-265166; no IRR database read has it.

Route objects not announced

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