bgpreport

Network · data from 2026-11-12

AS140864 RNLINK-AS-AP - R. N. Link

Registry name: RNLINK-AS-AP - R. N. Link, BD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140864, 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.
172.18.11.0/24 bogon No ROA None 0 0%low visibility 1

AS-SET

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

  • Bogon prefix1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Bogon prefix172.18.11.0/24In IANA's special-purpose registry: Private-Use (RFC 1918).0 of 673

Route objects not announced

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

2001:df4:1480::/48APNICValid

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.