bgpreport

Network · data from 2026-11-12

AS154690 VAYNE-AS-AP - VAYNE NETWORK PTE. LTD.

Registry name: VAYNE-AS-AP - VAYNE NETWORK PTE. LTD., SG · not in PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
0Route objects not announced registered with origin AS154690, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS154690, 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.
103.97.229.0/24 No ROA None 2 0%low visibility 2
87.86.191.0/24 Valid RIR databaseRADB, RIPE 669 99% 68
162.4.172.0/23 Valid RIR databaseAPNIC 669 99% 66
162.4.172.0/24 Valid RIR databaseAPNIC 669 99% 66
162.4.173.0/24 Valid RIR databaseAPNIC 669 99% 66
145.223.0.0/24 Valid RIR databaseRADB, RIPE 660 98% 66
2402:5fa0::/32 Valid RIR databaseAPNIC 631 99% 67
2402:5fa0:1::/48 Valid RIR databaseAPNIC 631 99% 67
2402:5fa0:a::/48 Valid RIR databaseAPNIC 631 99% 67

AS-SET

AS154690 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.

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none103.97.229.0/24No ROA covers it. Add a ROA for AS154690, maxLength 24.2 of 673
Route object: none103.97.229.0/24No route object for it. Add a route object with origin AS154690 in the RIR database for the space.2 of 673

Route objects not announced

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