bgpreport

Network · data from 2026-11-12

AS214478 Sakura Clouds LLC

Registry name: AS-SAKURACLOUDS Sakura Clouds LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214478, 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.
77.111.110.0/24 Invalid: origin None 3 0%low visibility 3
2a0f:85c1:861::/48 No ROA RIR databaseRIPE 636 100% 70
2a0f:85c1:863::/48 No ROA RIR databaseRIPE 636 100% 67
217.216.175.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
2a13:9500:76::/48 Valid RIR databaseRIPE 636 100% 69
2a14:67c1:b200::/48 Valid RIR databaseRIPE 636 100% 69
2a14:67c1:b203::/48 Valid RIR databaseRIPE 636 100% 69
2a14:67c1:b201::/48 Valid RIR databaseRIPE 634 100% 69
2a14:67c1:b202::/48 Valid RIR databaseRIPE 634 100% 67
2a14:67c1:b204::/48 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS214478: AS214478:AS-SAKURACLOUDS. 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 (AS214478 isn't in the set, or no route object for AS214478 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 objectsAS214478 in itNot covered
AS214478:AS-SAKURACLOUDS RIPE 2113 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 8 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin77.111.110.0/24ROAs covering it name AS834, AS21769, not AS214478. If AS214478 should announce it, add a ROA for AS214478.3 of 673
Route object: none77.111.110.0/24No route object for it. Add a route object with origin AS214478 in the RIR database for the space.3 of 673
ROA: none2a0f:85c1:861::/48No ROA covers it. Add a ROA for AS214478, maxLength 48.636 of 636
ROA: none2a0f:85c1:863::/48No ROA covers it. Add a ROA for AS214478, maxLength 48.636 of 636

Route objects not announced

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

2a0f:85c1:841::/48RIPEValid
2a0f:85c1:860::/48RIPEValid
2a0f:85c1:862::/48RIPENo ROA
2a14:67c1:b200::/40RIPEValid

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.