bgpreport

Network · data from 2026-11-12

AS45634 Sparkstation Pte Ltd

Registry name: SPARKSTATION-SG-AP - 10 Science Park Road, SG · PeeringDB

34IPv4 routes 100.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
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 AS45634, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45634, 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.
45.64.128.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
45.64.128.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
45.64.129.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
45.64.130.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
45.64.131.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.5.44.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
103.5.44.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.5.45.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.5.46.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.5.47.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.35.204.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
103.35.204.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.35.205.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.35.206.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.35.207.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.249.160.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
103.249.160.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.249.161.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.249.162.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.249.163.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
112.140.184.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
112.140.184.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
112.140.185.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
112.140.186.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
112.140.187.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
180.210.200.0/21 Valid RIR databaseAPNIC 673 100% 68
180.210.200.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
180.210.201.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
180.210.202.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
180.210.203.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
180.210.204.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
180.210.205.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
180.210.207.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
180.210.206.0/24 Valid RIR databaseAPNIC, RADB 670 100% 68
2401:c100::/32 Valid RIR databaseAPNIC, RADB 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS45634: RADB::AS45634:AS-ALL. 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 (AS45634 isn't in the set, or no route object for AS45634 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 objectsAS45634 in itNot covered
RADB::AS45634:AS-ALL RADB 4165 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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