bgpreport

Network · data from 2026-11-12

AS265056 NSLink Provedor de acesso internet

Registry name: AS265056 - NSLink Provedor de acesso internet LTDA-ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265056, 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.
170.231.148.0/24 No ROA Other IRR onlyRADB 670 100% 67
2804:321c::/32 No ROA Other IRR onlyTC 635 100% 67

AS-SET

AS265056'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 6 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none170.231.148.0/24No ROA covers it. Add a ROA for AS265056, maxLength 24.670 of 673
Route object: RIR170.231.148.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:321c::/32No ROA covers it. Add a ROA for AS265056, maxLength 32.635 of 636
Route object: RIR2804:321c::/32Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

170.231.148.0/22RADBNo ROA
170.231.148.0/23RADBNo 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.