bgpreport

Network · data from 2026-11-12

AS265117 Comp Telecom

Registry name: AS265117 - Comp Telecom, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265117, 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.
143.208.176.0/22 No ROA Other IRR onlyRADB, TC 671 100% 66
2804:2ac4::/32 No ROA Other IRR onlyRADB, TC 353 56% 65
143.208.176.0/24 No ROA Other IRR onlyRADB 196 29% 54
143.208.177.0/24 No ROA Other IRR onlyRADB 196 29% 54
143.208.178.0/24 No ROA Other IRR onlyRADB 196 29% 54
143.208.179.0/24 No ROA Other IRR onlyRADB 196 29% 54

AS-SET

PeeringDB's irr_as_set for AS265117: AS265117:AS-ALL. 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 (AS265117 isn't in the set, or no route object for AS265117 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 objectsAS265117 in itNot covered
AS265117:AS-ALL TC 126 Yes 0

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

  • ROA: none6
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none143.208.176.0/22No ROA covers it. Add a ROA for AS265117, maxLength 22.671 of 673
Route object: RIR143.208.176.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:2ac4::/32No ROA covers it. Add a ROA for AS265117, maxLength 32.353 of 636
Route object: RIR2804:2ac4::/32Route object only in RADB, TC. Add it in the RIR database for the space.353 of 636
ROA: none143.208.176.0/24No ROA covers it. Add a ROA for AS265117, maxLength 24.196 of 673
Route object: RIR143.208.176.0/24Route object only in RADB. Add it in the RIR database for the space.196 of 673
ROA: none143.208.177.0/24No ROA covers it. Add a ROA for AS265117, maxLength 24.196 of 673
Route object: RIR143.208.177.0/24Route object only in RADB. Add it in the RIR database for the space.196 of 673
ROA: none143.208.178.0/24No ROA covers it. Add a ROA for AS265117, maxLength 24.196 of 673
Route object: RIR143.208.178.0/24Route object only in RADB. Add it in the RIR database for the space.196 of 673
ROA: none143.208.179.0/24No ROA covers it. Add a ROA for AS265117, maxLength 24.196 of 673
Route object: RIR143.208.179.0/24Route object only in RADB. Add it in the RIR database for the space.196 of 673

Route objects not announced

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