bgpreport

Network · data from 2026-11-12

AS265913 Teleinfor

Registry name: AS265913 - TELEINFOR COMERCIO E SERVICO LTDA-ME, BR · PeeringDB

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

Announced routes

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

131.196.148.0/24 No ROA Nonecovered by 131.196.148.0/23 671 100% 67
131.196.149.0/24 No ROA Nonecovered by 131.196.148.0/23 671 100% 67
131.196.151.0/24 No ROA Nonecovered by 131.196.150.0/23 671 100% 67
131.196.150.0/24 No ROA Nonecovered by 131.196.150.0/23 669 99% 67
2804:3fc4:8000::/33 No ROA Nonecovered by 2804:3fc4::/32 635 100% 67
2804:3fc4:600::/47 No ROA Nonecovered by 2804:3fc4::/33 634 100% 67
131.196.148.0/22 No ROA Other IRR onlyRADB, TC 673 100% 67
2804:3fc4::/33 No ROA Other IRR onlyTC 635 100% 67
2804:3fc4::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS265913: AS265913: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 (AS265913 isn't in the set, or no route object for AS265913 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 objectsAS265913 in itNot covered
AS265913:AS-ANNOUNCEMENTS TC 125 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 20 are in fix.csv.

  • ROA: none9
  • Route object: none6
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none131.196.148.0/24No ROA covers it. Add a ROA for AS265913, maxLength 24.671 of 673
Route object: none131.196.148.0/24No route object for it. A route object for 131.196.148.0/23 with origin AS265913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265913 in the RIR database for the space.671 of 673
ROA: none131.196.149.0/24No ROA covers it. Add a ROA for AS265913, maxLength 24.671 of 673
Route object: none131.196.149.0/24No route object for it. A route object for 131.196.148.0/23 with origin AS265913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265913 in the RIR database for the space.671 of 673
ROA: none131.196.151.0/24No ROA covers it. Add a ROA for AS265913, maxLength 24.671 of 673
Route object: none131.196.151.0/24No route object for it. A route object for 131.196.150.0/23 with origin AS265913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265913 in the RIR database for the space.671 of 673
ROA: none131.196.150.0/24No ROA covers it. Add a ROA for AS265913, maxLength 24.669 of 673
Route object: none131.196.150.0/24No route object for it. A route object for 131.196.150.0/23 with origin AS265913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265913 in the RIR database for the space.669 of 673
ROA: none2804:3fc4:8000::/33No ROA covers it. Add a ROA for AS265913, maxLength 33.635 of 636
Route object: none2804:3fc4:8000::/33No route object for it. A route object for 2804:3fc4::/32 with origin AS265913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265913 in the RIR database for the space.635 of 636
ROA: none2804:3fc4:600::/47No ROA covers it. Add a ROA for AS265913, maxLength 47.634 of 636
Route object: none2804:3fc4:600::/47No route object for it. A route object for 2804:3fc4::/33 with origin AS265913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265913 in the RIR database for the space.634 of 636
ROA: none131.196.148.0/22No ROA covers it. Add a ROA for AS265913, maxLength 22.673 of 673
Route object: RIR131.196.148.0/22Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
ROA: none2804:3fc4::/33No ROA covers it. Add a ROA for AS265913, maxLength 33.635 of 636
Route object: RIR2804:3fc4::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:3fc4::/32No ROA covers it. Add a ROA for AS265913, maxLength 32.634 of 636
Route object: RIR2804:3fc4::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

131.196.148.0/23TCNo ROA
131.196.150.0/23TCNo 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.