bgpreport

Network · data from 2026-11-12

AS267642 T. TELES LEITE TELECOMUNICACOES

Registry name: AS267642 - T. TELES LEITE TELECOMUNICACOES LTDA ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267642, 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.

45.71.192.0/23 No ROA Nonecovered by 45.71.192.0/22 671 100% 67
45.71.194.0/23 No ROA Nonecovered by 45.71.192.0/22 671 100% 67
2804:449c::/40 No ROA Nonecovered by 2804:449c::/32 449 71% 64
45.71.193.0/24 No ROA Nonecovered by 45.71.192.0/22 5 1%low visibility 3
45.71.192.0/24 No ROA Nonecovered by 45.71.192.0/22 3 0%low visibility 3
45.71.194.0/24 No ROA Nonecovered by 45.71.192.0/22 3 0%low visibility 3
45.71.195.0/24 No ROA Nonecovered by 45.71.192.0/22 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS267642: AS-SET. 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 (AS267642 isn't in the set, or no route object for AS267642 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 objectsAS267642 in itNot covered
AS-SET RADB 010 No 7
AFRINIC (also) 111 No 7
ARIN (also) 010 No 7
RIPE (also)1 member set in no database: AS200105:AS-HK 38151,451 No 7

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: none7
  • Route object: none7
  • AS-SET: own ASN1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.71.192.0/23No ROA covers it. Add a ROA for AS267642, maxLength 23.671 of 673
Route object: none45.71.192.0/23No route object for it. A route object for 45.71.192.0/22 with origin AS267642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267642 in the RIR database for the space.671 of 673
ROA: none45.71.194.0/23No ROA covers it. Add a ROA for AS267642, maxLength 23.671 of 673
Route object: none45.71.194.0/23No route object for it. A route object for 45.71.192.0/22 with origin AS267642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267642 in the RIR database for the space.671 of 673
ROA: none2804:449c::/40No ROA covers it. Add a ROA for AS267642, maxLength 40.449 of 636
Route object: none2804:449c::/40No route object for it. A route object for 2804:449c::/32 with origin AS267642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267642 in the RIR database for the space.449 of 636
ROA: none45.71.193.0/24No ROA covers it. Add a ROA for AS267642, maxLength 24.5 of 673
Route object: none45.71.193.0/24No route object for it. A route object for 45.71.192.0/22 with origin AS267642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267642 in the RIR database for the space.5 of 673
ROA: none45.71.192.0/24No ROA covers it. Add a ROA for AS267642, maxLength 24.3 of 673
Route object: none45.71.192.0/24No route object for it. A route object for 45.71.192.0/22 with origin AS267642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267642 in the RIR database for the space.3 of 673
ROA: none45.71.194.0/24No ROA covers it. Add a ROA for AS267642, maxLength 24.3 of 673
Route object: none45.71.194.0/24No route object for it. A route object for 45.71.192.0/22 with origin AS267642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267642 in the RIR database for the space.3 of 673
ROA: none45.71.195.0/24No ROA covers it. Add a ROA for AS267642, maxLength 24.3 of 673
Route object: none45.71.195.0/24No route object for it. A route object for 45.71.192.0/22 with origin AS267642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267642 in the RIR database for the space.3 of 673
AS-SET: own ASNAS-SETAS267642 isn't in AS-SET (RADB) once expanded. Add AS267642 to it.

Route objects not announced

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

45.71.192.0/22RADBNo ROA
2804:449c::/32RADBNo ROA

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.