bgpreport

Network · data from 2026-11-12

AS212890 ONEMAN NETWORK LIMITED

Registry name: AetherCloud ONEMAN NETWORK LIMITED, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS212890, 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.

66.85.45.0/24 No ROA Other origin only 2 0%low visibility 2
2a14:67c3:13::/48 Valid None 634 100% 69
2a14:67c3:14::/48 Valid None 631 99% 67
2a14:67c3:12::/48 Valid None 1 0%low visibility 1
2602:faa8:502::/48 Valid RIR databaseARIN 634 100% 69
162.251.204.0/24 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

AS212890'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 8 are in fix.csv.

  • ROA: none1
  • Route object: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none66.85.45.0/24No ROA covers it. Add a ROA for AS212890, maxLength 24.2 of 673
Route object: none66.85.45.0/24Route objects for it name AS31863, AS40676, AS393960. Add a route object with origin AS212890 in the RIR database for the space.2 of 673
Route object: none2a14:67c3:13::/48No route object for it. Add a route object with origin AS212890 in the RIR database for the space.634 of 636
Route object: none2a14:67c3:14::/48No route object for it. Add a route object with origin AS212890 in the RIR database for the space.631 of 636
Route object: none2a14:67c3:12::/48No route object for it. Add a route object with origin AS212890 in the RIR database for the space.1 of 636

Route objects not announced

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

2401:b60:3c::/48APNICValid
2602:faa8:501::/48ARINValid
2602:faa8:503::/48ARINValid

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.