bgpreport

Network · data from 2026-11-12

AS265214 RENATO ANTONIO DA SILVA ME

Registry name: AS265214 - NT NET TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265214, 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.
167.250.156.0/23 No ROA Nonecovered by 167.250.156.0/22 672 100% 67
167.250.156.0/22 No ROA Other IRR onlyRADB 671 100% 67
2804:2c5c::/33 No ROA Other IRR onlyRADB 634 100% 67
167.250.156.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
167.250.157.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
167.250.158.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
167.250.159.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS265214's PeeringDB record names no AS-SET.

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

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none167.250.156.0/23No ROA covers it. Add a ROA for AS265214, maxLength 23.672 of 673
Route object: none167.250.156.0/23No route object for it. A route object for 167.250.156.0/22 with origin AS265214 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265214 in the RIR database for the space.672 of 673
ROA: none167.250.156.0/22No ROA covers it. Add a ROA for AS265214, maxLength 22.671 of 673
Route object: RIR167.250.156.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:2c5c::/33No ROA covers it. Add a ROA for AS265214, maxLength 33.634 of 636
Route object: RIR2804:2c5c::/33Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none167.250.156.0/24No ROA covers it. Add a ROA for AS265214, maxLength 24.2 of 673
Route object: RIR167.250.156.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none167.250.157.0/24No ROA covers it. Add a ROA for AS265214, maxLength 24.2 of 673
Route object: RIR167.250.157.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none167.250.158.0/24No ROA covers it. Add a ROA for AS265214, maxLength 24.2 of 673
Route object: RIR167.250.158.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none167.250.159.0/24No ROA covers it. Add a ROA for AS265214, maxLength 24.2 of 673
Route object: RIR167.250.159.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

2804:2c5c::/32RADBNo ROA
2804:2c5c::/34RADBNo ROA
2804:2c5c:4000::/34RADBNo ROA
2804:2c5c:8000::/33RADBNo 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.