bgpreport

Network · data from 2026-11-12

AS149042 SiliCloud

Registry name: SITCL-AS-AP - Silicon Cloud Global (US), HK · PeeringDB

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

Announced routes

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

154.19.186.59/32 Invalid: maxLength Nonecovered by 154.19.186.0/24 2 0%low visibility 3
154.19.184.0/23 Valid Other IRR onlyRADB 670 100% 67
38.47.52.0/23 Valid Other IRR onlyRADB 669 99% 67
38.47.54.0/23 Valid Other IRR onlyRADB 669 99% 67
103.214.168.0/23 Valid Other IRR onlyJPIRR 669 99% 67
103.214.168.0/24 Valid Other IRR onlyJPIRR 669 99% 67
103.214.169.0/24 Valid Other IRR onlyJPIRR 669 99% 67
154.19.186.0/23 Valid Other IRR onlyRADB 669 99% 67
154.19.187.0/24 Valid Other IRR onlyRADB 669 99% 67
103.150.180.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.177.80.0/23 Valid RIR databaseAPNIC 673 100% 67
2400:38e0:1::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2400:38e0:200::/40 Valid RIR databaseAPNIC 635 100% 69
2400:38e0::/48 Valid RIR databaseAPNIC 633 100% 68

AS-SET

PeeringDB's irr_as_set for AS149042: AS149042:AS-SICLOUD. 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 (AS149042 isn't in the set, or no route object for AS149042 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 objectsAS149042 in itNot covered
AS149042:AS-SICLOUD APNIC 1123 Yes 1

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

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: maxLength154.19.186.59/32ROA 154.19.184.0/22 AS149042 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 154.19.186.59/32.2 of 673
Route object: none154.19.186.59/32No route object for it. A route object for 154.19.186.0/24 with origin AS149042 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS149042 in the RIR database for the space.2 of 673
Route object: RIR154.19.184.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR38.47.52.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.47.54.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR103.214.168.0/23Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
Route object: RIR103.214.168.0/24Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
Route object: RIR103.214.169.0/24Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
Route object: RIR154.19.186.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR154.19.187.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

38.47.52.0/22ARINValid
38.47.52.0/24RADBValid
38.47.53.0/24RADBValid
38.47.54.0/24RADBValid
38.47.55.0/24RADBValid
154.19.184.0/22ARINValid
154.19.184.0/24RADBValid
154.19.185.0/24RADBValid
154.19.186.0/24RADBValid
2400:38e0:100::/40APNICValid

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.