bgpreport

Network · data from 2026-11-12

AS9423 ServerKing.io AS9423

Registry name: SERVERKINGIOLLC-AS-AP - ServerKing.io, LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9423, 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.
23.147.184.0/24 Valid RIR databaseARIN 671 100% 68
103.31.116.0/24 Valid RIR databaseAPNIC 671 100% 68
103.31.117.0/24 Valid RIR databaseAPNIC 671 100% 68
140.235.249.0/24 Valid RIR databaseARIN 671 100% 68
204.126.106.0/23 Valid RIR databaseARIN 671 100% 68
2001:df1:7f40::/48 Valid RIR databaseAPNIC 636 100% 69
2001:df1:7f41::/48 Valid RIR databaseAPNIC 636 100% 69
2001:df1:7f42::/48 Valid RIR databaseAPNIC 636 100% 69
2001:df1:7f43::/48 Valid RIR databaseAPNIC 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS9423: AS9423:AS-SERVERKING. 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 (AS9423 isn't in the set, or no route object for AS9423 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 objectsAS9423 in itNot covered
AS9423:AS-SERVERKING APNIC1 member set in no database: AS9423:AS-CUSTOMERS 119 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 1 are in fix.csv.

  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS9423:AS-SERVERKINGAS9423:AS-SERVERKING (APNIC) lists AS9423:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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