bgpreport

Network · data from 2026-11-12

AS266275 JEFFERSON KAYAM DA ROCHA

Registry name: AS266275 - ITELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266275, 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.
170.78.180.0/24 Valid Nonecovered by 170.78.180.0/23 669 99% 67
2804:3538:8000::/33 Valid Nonecovered by 2804:3538::/32 633 100% 67
2804:3538::/34 Valid Nonecovered by 2804:3538::/32 350 55% 64
2804:3538:4000::/34 Valid Nonecovered by 2804:3538::/32 350 55% 64
2804:3538:8000::/34 Valid Nonecovered by 2804:3538::/32 350 55% 64
2804:3538:c000::/34 Valid Nonecovered by 2804:3538::/32 350 55% 64
170.78.181.0/24 Valid Nonecovered by 170.78.180.0/23 195 29% 54
170.78.182.0/24 Valid Nonecovered by 170.78.180.0/22 195 29% 54
170.78.183.0/24 Valid Nonecovered by 170.78.180.0/22 195 29% 54
170.78.180.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
170.78.180.0/23 Valid Other IRR onlyRADB 672 100% 66
2804:3538::/32 Valid Other IRR onlyALTDB, RADB, TC 632 99% 67

AS-SET

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

  • Route object: none9
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
Route object: none170.78.180.0/24No route object for it. A route object for 170.78.180.0/23 with origin AS266275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266275 in the RIR database for the space.669 of 673
Route object: none2804:3538:8000::/33No route object for it. A route object for 2804:3538::/32 with origin AS266275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266275 in the RIR database for the space.633 of 636
Route object: none2804:3538::/34No route object for it. A route object for 2804:3538::/32 with origin AS266275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266275 in the RIR database for the space.350 of 636
Route object: none2804:3538:4000::/34No route object for it. A route object for 2804:3538::/32 with origin AS266275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266275 in the RIR database for the space.350 of 636
Route object: none2804:3538:8000::/34No route object for it. A route object for 2804:3538::/32 with origin AS266275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266275 in the RIR database for the space.350 of 636
Route object: none2804:3538:c000::/34No route object for it. A route object for 2804:3538::/32 with origin AS266275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266275 in the RIR database for the space.350 of 636
Route object: none170.78.181.0/24No route object for it. A route object for 170.78.180.0/23 with origin AS266275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266275 in the RIR database for the space.195 of 673
Route object: none170.78.182.0/24No route object for it. A route object for 170.78.180.0/22 with origin AS266275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266275 in the RIR database for the space.195 of 673
Route object: none170.78.183.0/24No route object for it. A route object for 170.78.180.0/22 with origin AS266275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266275 in the RIR database for the space.195 of 673
Route object: RIR170.78.180.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.78.180.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:3538::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.632 of 636

Route objects not announced

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