bgpreport

Network · data from 2026-11-12

AS138456 OceanBlue Cloud Technology

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS138456, 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.134.174.0/24 No ROA Other IRR onlyRADB 671 100% 68
38.247.81.0/24 No ROA Other IRR onlyRADB 671 100% 68
38.46.158.0/23 No ROA Other IRR onlyRADB 670 100% 68
45.194.96.0/24 No ROA RIR databaseAFRINIC 670 100% 68
45.195.136.0/24 Valid Other IRR onlyRADB 670 100% 69
103.126.24.0/24 Valid RIR databaseAPNIC 671 100% 68
145.79.179.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
145.79.180.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
45.202.194.0/23 Valid RIR databaseAFRINIC 670 100% 68
45.202.196.0/24 Valid RIR databaseAFRINIC 670 100% 68
154.197.52.0/23 Valid RIR databaseAFRINIC 670 100% 68
154.197.76.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 68
154.211.3.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 68
154.213.1.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 68
154.213.2.0/23 Valid RIR databaseAFRINIC, RADB 670 100% 68
156.252.21.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 68
2001:df7:3700::/48 Valid RIR databaseAPNIC 634 100% 69

AS-SET

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

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none38.134.174.0/24No ROA covers it. Add a ROA for AS138456, maxLength 24.671 of 673
Route object: RIR38.134.174.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.247.81.0/24No ROA covers it. Add a ROA for AS138456, maxLength 24.671 of 673
Route object: RIR38.247.81.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.46.158.0/23No ROA covers it. Add a ROA for AS138456, maxLength 23.670 of 673
Route object: RIR38.46.158.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.194.96.0/24No ROA covers it. Add a ROA for AS138456, maxLength 24.670 of 673
Route object: RIR45.195.136.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

45.194.97.0/24AFRINICNo ROA
154.194.41.0/24AFRINIC, RADBValid
154.194.42.0/24AFRINIC, RADBValid
154.213.2.0/24RADBValid
154.213.3.0/24RADBValid
2001:470:271::/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.