bgpreport

Network · data from 2026-11-12

AS401439 NEIGHBOURHOOD-CONNECT-2 - Neighbourhood Connect

Registry name: NEIGHBOURHOOD-CONNECT-2 - Neighbourhood Connect, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401439, 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.
38.69.161.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS401439 isn't in PeeringDB, where networks name their 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 3 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.69.161.0/24No ROA covers it. Add a ROA for AS401439, maxLength 24.671 of 673
Route object: RIR38.69.161.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

168.151.158.0/23ARINNo 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.