bgpreport

Network · data from 2026-11-12

AS265041 Infotel Engenharia e Telecomunicações SCM

Registry name: AS265041 - INFOTEL ENGENHARIA & TELECOMUNICACOES SCM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265041, 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.
201.7.220.0/24 Valid Nonecovered by 201.7.220.0/23 2 0%low visibility 2
201.7.221.0/24 Valid Nonecovered by 201.7.220.0/23 2 0%low visibility 2
45.237.148.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
170.150.136.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
201.7.220.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
2804:31dc::/32 Valid Other IRR onlyRADB, TC 631 99% 67
45.237.148.0/23 Valid Other IRR onlyTC 196 29% 56
45.237.150.0/23 Valid Other IRR onlyTC 196 29% 56
170.150.138.0/23 Valid Other IRR onlyTC 196 29% 56
201.7.220.0/23 Valid Other IRR onlyTC 196 29% 56
201.7.222.0/23 Valid Other IRR onlyTC 196 29% 56
170.150.136.0/23 Valid Other IRR onlyTC 195 29% 56
45.237.148.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
45.237.149.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
45.237.150.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
45.237.151.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
170.150.136.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
170.150.137.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
170.150.138.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
170.150.139.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
201.7.222.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
201.7.223.0/24 Valid Other IRR onlyTC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS265041: AS-INFOTEL. 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 (AS265041 isn't in the set, or no route object for AS265041 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 objectsAS265041 in itNot covered
AS-INFOTEL RIPE 112 No 22

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

  • Route object: none2
  • Route object: RIR20
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
Route object: none201.7.220.0/24No route object for it. A route object for 201.7.220.0/23 with origin AS265041 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265041 in the RIR database for the space.2 of 673
Route object: none201.7.221.0/24No route object for it. A route object for 201.7.220.0/23 with origin AS265041 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265041 in the RIR database for the space.2 of 673
Route object: RIR45.237.148.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.150.136.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR201.7.220.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:31dc::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR45.237.148.0/23Route object only in TC. Add it in the RIR database for the space.196 of 673
Route object: RIR45.237.150.0/23Route object only in TC. Add it in the RIR database for the space.196 of 673
Route object: RIR170.150.138.0/23Route object only in TC. Add it in the RIR database for the space.196 of 673
Route object: RIR201.7.220.0/23Route object only in TC. Add it in the RIR database for the space.196 of 673
Route object: RIR201.7.222.0/23Route object only in TC. Add it in the RIR database for the space.196 of 673
Route object: RIR170.150.136.0/23Route object only in TC. Add it in the RIR database for the space.195 of 673
Route object: RIR45.237.148.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR45.237.149.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR45.237.150.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR45.237.151.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR170.150.136.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR170.150.137.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR170.150.138.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR170.150.139.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR201.7.222.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR201.7.223.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
AS-SET: own ASNAS-INFOTELAS265041 isn't in AS-INFOTEL (RIPE) once expanded. Add AS265041 to it.

Route objects not announced

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