bgpreport

Network · data from 2026-11-12

AS264933 NTi Telecomunicações LTDA.

Registry name: AS264933 - NTi Telecomunicacoes LTDA., BR · PeeringDB

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

Announced routes

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

168.232.42.0/24 No ROA Nonecovered by 168.232.40.0/22 672 100% 66
168.232.41.0/24 No ROA Nonecovered by 168.232.40.0/22 671 100% 66
168.232.43.0/24 No ROA Nonecovered by 168.232.40.0/22 671 100% 66
168.232.40.0/24 No ROA Nonecovered by 168.232.40.0/22 670 100% 66
168.232.40.0/22 No ROA Other IRR onlyRADB 672 100% 66
2804:3028::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS264933: AS-264933. 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 (AS264933 isn't in the set, or no route object for AS264933 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 objectsAS264933 in itNot covered
AS-264933 In no IRR database read today.

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

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none168.232.42.0/24No ROA covers it. Add a ROA for AS264933, maxLength 24.672 of 673
Route object: none168.232.42.0/24No route object for it. A route object for 168.232.40.0/22 with origin AS264933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264933 in the RIR database for the space.672 of 673
ROA: none168.232.41.0/24No ROA covers it. Add a ROA for AS264933, maxLength 24.671 of 673
Route object: none168.232.41.0/24No route object for it. A route object for 168.232.40.0/22 with origin AS264933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264933 in the RIR database for the space.671 of 673
ROA: none168.232.43.0/24No ROA covers it. Add a ROA for AS264933, maxLength 24.671 of 673
Route object: none168.232.43.0/24No route object for it. A route object for 168.232.40.0/22 with origin AS264933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264933 in the RIR database for the space.671 of 673
ROA: none168.232.40.0/24No ROA covers it. Add a ROA for AS264933, maxLength 24.670 of 673
Route object: none168.232.40.0/24No route object for it. A route object for 168.232.40.0/22 with origin AS264933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264933 in the RIR database for the space.670 of 673
ROA: none168.232.40.0/22No ROA covers it. Add a ROA for AS264933, maxLength 22.672 of 673
Route object: RIR168.232.40.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:3028::/32No ROA covers it. Add a ROA for AS264933, maxLength 32.636 of 636
Route object: RIR2804:3028::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
AS-SET: not foundAS-264933PeeringDB names AS-264933; no IRR database read has it.

Route objects not announced

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