bgpreport

Network · data from 2026-11-12

AS264562 Texnet Internet Fibra Óptica

Registry name: AS264562 - PBR SERVICOS DE TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

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

191.128.58.0/24 No ROA None 671 100% 67
191.128.61.0/24 No ROA None 671 100% 67
191.128.58.0/23 No ROA Other origin only 670 100% 67
191.128.60.0/24 No ROA None 2 0%low visibility 2
191.128.59.0/24 No ROA Other IRR onlyRADB 673 100% 66
191.128.52.0/24 No ROA Other IRR onlyRADB 672 100% 66
191.128.57.0/24 No ROA Other IRR onlyRADB 671 100% 67
191.128.240.0/24 No ROA Other IRR onlyRADB 671 100% 67
191.128.56.0/24 No ROA Other IRR onlyRADB 667 99% 67
2804:2190:4010::/44 Valid Nonecovered by 2804:2190:4000::/34 634 100% 67
2804:2190:4010::/48 Valid Nonecovered by 2804:2190:4000::/34 634 100% 67
45.239.8.0/24 Valid Other IRR onlyRADB, TC 673 100% 66
45.174.188.0/23 Valid Other IRR onlyTC 672 100% 66
45.174.191.0/24 Valid Other IRR onlyTC 672 100% 66
138.36.0.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
138.36.0.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
168.232.84.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
168.232.86.0/23 Valid Other IRR onlyTC 672 100% 66
187.49.176.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
187.49.177.0/24 Valid Other IRR onlyTC 672 100% 66
45.239.11.0/24 Valid Other IRR onlyTC 671 100% 66
138.36.2.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
168.232.84.0/23 Valid Other IRR onlyTC 671 100% 67
187.49.176.0/23 Valid Other IRR onlyTC 671 100% 67
187.49.178.0/23 Valid Other IRR onlyTC 671 100% 67
45.174.190.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
45.239.9.0/24 Valid Other IRR onlyTC 668 99% 67
45.239.10.0/24 Valid Other IRR onlyTC 667 99% 67
2804:2190:4000::/48 Valid Other IRR onlyRADB 634 100% 67
2804:2190::/32 Valid Other IRR onlyRADB, TC 633 100% 67
2804:2190:8000::/33 Valid Other IRR onlyTC 633 100% 67
2804:2190::/33 Valid Other IRR onlyTC 630 99% 67
2804:2190::/34 Valid Other IRR onlyTC 349 55% 65
2804:2190:4000::/34 Valid Other IRR onlyTC 349 55% 65
2804:2190:8000::/34 Valid Other IRR onlyTC 349 55% 65
2804:2190:c000::/34 Valid Other IRR onlyTC 349 55% 65
138.36.0.0/24 Valid Other IRR onlyTC 198 29% 56
138.36.1.0/24 Valid Other IRR onlyTC 198 29% 56
138.36.2.0/24 Valid Other IRR onlyTC 198 29% 56
138.36.3.0/24 Valid Other IRR onlyTC 198 29% 56
187.49.176.0/24 Valid Other IRR onlyTC 198 29% 56
187.49.178.0/24 Valid Other IRR onlyTC 198 29% 56
187.49.179.0/24 Valid Other IRR onlyTC 198 29% 56
45.174.188.0/24 Valid Other IRR onlyTC 197 29% 56
168.232.84.0/24 Valid Other IRR onlyTC 197 29% 56
168.232.85.0/24 Valid Other IRR onlyTC 197 29% 56
168.232.87.0/24 Valid Other IRR onlyTC 197 29% 56
45.174.189.0/24 Valid Other IRR onlyTC 195 29% 56
168.232.86.0/24 Valid Other IRR onlyTC 195 29% 56
38.21.121.0/24 Valid RIR databaseARIN 671 100% 67
38.210.119.0/24 Valid RIR databaseARIN 671 100% 67
38.236.99.0/24 Valid RIR databaseARIN 670 100% 67
38.225.111.0/24 Valid RIR databaseARIN 669 99% 66

AS-SET

PeeringDB's irr_as_set for AS264562: AS264562:AS-ANNOUNCEMENTS. 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 (AS264562 isn't in the set, or no route object for AS264562 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 objectsAS264562 in itNot covered
AS264562:AS-ANNOUNCEMENTS TC1 member set in no database: AS268944:AS-MARTINSTELECOM 2823270 Yes 4

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

  • ROA: none9
  • Route object: none6
  • Route object: RIR43
  • AS-SET: missing member1
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none191.128.58.0/24No ROA covers it. Add a ROA for AS264562, maxLength 24.671 of 673
Route object: none191.128.58.0/24No route object for it. Add a route object with origin AS264562 in the RIR database for the space.671 of 673
ROA: none191.128.61.0/24No ROA covers it. Add a ROA for AS264562, maxLength 24.671 of 673
Route object: none191.128.61.0/24No route object for it. Add a route object with origin AS264562 in the RIR database for the space.671 of 673
ROA: none191.128.58.0/23No ROA covers it. Add a ROA for AS264562, maxLength 23.670 of 673
Route object: none191.128.58.0/23Route objects for it name AS26615. Add a route object with origin AS264562 in the RIR database for the space.670 of 673
ROA: none191.128.60.0/24No ROA covers it. Add a ROA for AS264562, maxLength 24.2 of 673
Route object: none191.128.60.0/24No route object for it. Add a route object with origin AS264562 in the RIR database for the space.2 of 673
ROA: none191.128.59.0/24No ROA covers it. Add a ROA for AS264562, maxLength 24.673 of 673
Route object: RIR191.128.59.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none191.128.52.0/24No ROA covers it. Add a ROA for AS264562, maxLength 24.672 of 673
Route object: RIR191.128.52.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none191.128.57.0/24No ROA covers it. Add a ROA for AS264562, maxLength 24.671 of 673
Route object: RIR191.128.57.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none191.128.240.0/24No ROA covers it. Add a ROA for AS264562, maxLength 24.671 of 673
Route object: RIR191.128.240.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none191.128.56.0/24No ROA covers it. Add a ROA for AS264562, maxLength 24.667 of 673
Route object: RIR191.128.56.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: none2804:2190:4010::/44No route object for it. A route object for 2804:2190:4000::/34 with origin AS264562 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264562 in the RIR database for the space.634 of 636
Route object: none2804:2190:4010::/48No route object for it. A route object for 2804:2190:4000::/34 with origin AS264562 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264562 in the RIR database for the space.634 of 636
Route object: RIR45.239.8.0/24Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
Route object: RIR45.174.188.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.174.191.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.36.0.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.36.0.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.232.84.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.232.86.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.49.176.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.49.177.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.239.11.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.36.2.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR168.232.84.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.176.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.178.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.174.190.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.239.9.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.239.10.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:2190:4000::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:2190::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:2190:8000::/33Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:2190::/33Route object only in TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:2190::/34Route object only in TC. Add it in the RIR database for the space.349 of 636
Route object: RIR2804:2190:4000::/34Route object only in TC. Add it in the RIR database for the space.349 of 636
Route object: RIR2804:2190:8000::/34Route object only in TC. Add it in the RIR database for the space.349 of 636
Route object: RIR2804:2190:c000::/34Route object only in TC. Add it in the RIR database for the space.349 of 636
Route object: RIR138.36.0.0/24Route object only in TC. Add it in the RIR database for the space.198 of 673
Route object: RIR138.36.1.0/24Route object only in TC. Add it in the RIR database for the space.198 of 673
Route object: RIR138.36.2.0/24Route object only in TC. Add it in the RIR database for the space.198 of 673
Route object: RIR138.36.3.0/24Route object only in TC. Add it in the RIR database for the space.198 of 673
Route object: RIR187.49.176.0/24Route object only in TC. Add it in the RIR database for the space.198 of 673
Route object: RIR187.49.178.0/24Route object only in TC. Add it in the RIR database for the space.198 of 673
Route object: RIR187.49.179.0/24Route object only in TC. Add it in the RIR database for the space.198 of 673
Route object: RIR45.174.188.0/24Route object only in TC. Add it in the RIR database for the space.197 of 673
Route object: RIR168.232.84.0/24Route object only in TC. Add it in the RIR database for the space.197 of 673
Route object: RIR168.232.85.0/24Route object only in TC. Add it in the RIR database for the space.197 of 673
Route object: RIR168.232.87.0/24Route object only in TC. Add it in the RIR database for the space.197 of 673
Route object: RIR45.174.189.0/24Route object only in TC. Add it in the RIR database for the space.195 of 673
Route object: RIR168.232.86.0/24Route object only in TC. Add it in the RIR database for the space.195 of 673
AS-SET: missing memberAS264562:AS-ANNOUNCEMENTSAS264562:AS-ANNOUNCEMENTS (TC) lists AS268944:AS-MARTINSTELECOM; no IRR database read has it.

Route objects not announced

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

45.174.188.0/22RADB, TCValid
45.174.190.0/23TCValid
45.239.8.0/22RADB, TCValid
45.239.8.0/23TCValid
45.239.10.0/23TCValid
191.128.48.0/23RADBNo ROA
191.128.48.0/24RADBNo ROA
191.128.50.0/23RADBNo ROA
191.128.50.0/24RADBNo ROA
191.128.52.0/23RADBNo ROA
191.128.53.0/24RADBNo ROA
191.128.54.0/23RADBNo ROA
191.128.54.0/24RADBNo ROA
191.128.55.0/24RADBNo ROA
191.128.56.0/23RADBNo ROA
191.128.240.0/23RADBNo ROA
2804:2190:c000::/36TCValid

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.