bgpreport

Network · data from 2026-11-12

AS154346 OceanBlue Cloud Technology Limited

Registry name: OCTL-AS-AP - OceanBlue Cloud Technology Limited, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS154346, 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.
202.134.239.0/24 Invalid: origin Other origin only 1 0%low visibility 1
2001:df7:3700::/46 No ROA None 635 100% 68
38.22.124.0/24 No ROA None 82 12% 38
154.50.40.0/24 No ROA RIR databaseARIN 673 100% 67
154.50.39.0/24 Valid RIR databaseARIN 673 100% 67
103.152.206.0/24 Valid RIR databaseAPNIC 671 100% 67
2001:df7:3701::/48 Valid RIR databaseAPNIC 635 100% 68

AS-SET

PeeringDB's irr_as_set for AS154346: APNIC::AS138456:AS-OCEANBLUE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS154346 isn't in the set, or no route object for AS154346 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS154346 in itNot covered
APNIC::AS138456:AS-OCEANBLUE APNIC 4136 Yes 3

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

  • ROA: origin1
  • ROA: none3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: origin202.134.239.0/24ROAs covering it name AS7346, not AS154346. If AS154346 should announce it, add a ROA for AS154346.1 of 673
Route object: none202.134.239.0/24Route objects for it name AS7346. Add a route object with origin AS154346 in the RIR database for the space.1 of 673
ROA: none2001:df7:3700::/46No ROA covers it. Add a ROA for AS154346, maxLength 46.635 of 636
Route object: none2001:df7:3700::/46No route object for it. Add a route object with origin AS154346 in the RIR database for the space.635 of 636
ROA: none38.22.124.0/24No ROA covers it. Add a ROA for AS154346, maxLength 24.82 of 673
Route object: none38.22.124.0/24No route object for it. Add a route object with origin AS154346 in the RIR database for the space.82 of 673
ROA: none154.50.40.0/24No ROA covers it. Add a ROA for AS154346, maxLength 24.673 of 673

Route objects not announced

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