bgpreport

Network · data from 2026-11-12

AS47778 Sunoaki Network Backbone

Registry name: SUNOAKI-NET-BACKBONE Sunoaki Network LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47778, 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.
2a13:a5c7:1001::/48 Valid Nonecovered by 2a13:a5c7:1000::/46 635 100% 69
2a13:a5c7:1002::/48 Valid Nonecovered by 2a13:a5c7:1000::/46 5 1%low visibility 4
2602:2a3:7::/48 Valid RIR databaseARIN 636 100% 69
2602:2a3:2::/48 Valid RIR databaseARIN 635 100% 69
2602:2a3:3::/48 Valid RIR databaseARIN 635 100% 69
2602:2a3:5::/48 Valid RIR databaseARIN 635 100% 69
2602:2a3:12::/48 Valid RIR databaseARIN 635 100% 69
2602:2a3:9::/48 Valid RIR databaseARIN 634 100% 69
2602:2a3:10::/48 Valid RIR databaseARIN 634 100% 69
2602:2a3:13::/48 Valid RIR databaseARIN 634 100% 69
2a13:a5c7:1000::/46 Valid RIR databaseALTDB, RADB, RIPE 351 55% 64
2602:2a3:11::/48 Valid RIR databaseARIN 5 1%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS47778: ARIN::AS-SUNOAKI. 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 (AS47778 isn't in the set, or no route object for AS47778 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 objectsAS47778 in itNot covered
ARIN::AS-SUNOAKI ARIN 6813,036 Yes 0

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

  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2a13:a5c7:1001::/48No route object for it. A route object for 2a13:a5c7:1000::/46 with origin AS47778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47778 in the RIR database for the space.635 of 636
Route object: none2a13:a5c7:1002::/48No route object for it. A route object for 2a13:a5c7:1000::/46 with origin AS47778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47778 in the RIR database for the space.5 of 636

Route objects not announced

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

23.163.8.0/24ARINValid

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.