bgpreport

Network · data from 2026-11-12

AS47063 SWITCHSPACE - Switchspace Inc.

Registry name: SWITCHSPACE - Switchspace Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47063, 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.
162.219.79.0/24 Valid Nonecovered by 162.219.76.0/22 673 100% 67
208.185.113.0/24 Valid None 673 100% 67
162.219.76.0/24 Valid Other origin onlycovered by 162.219.76.0/22 672 100% 67
162.219.78.0/24 Valid Other origin onlycovered by 162.219.76.0/22 672 100% 67

AS-SET

AS47063 isn't in PeeringDB, where networks name their AS-SET.

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

  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none162.219.79.0/24No route object for it. A route object for 162.219.76.0/22 with origin AS47063 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47063 in the RIR database for the space.673 of 673
Route object: none208.185.113.0/24No route object for it. Add a route object with origin AS47063 in the RIR database for the space.673 of 673
Route object: none162.219.76.0/24Route objects for it name AS393989. A route object for 162.219.76.0/22 with origin AS47063 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47063 in the RIR database for the space.672 of 673
Route object: none162.219.78.0/24Route objects for it name AS393989. A route object for 162.219.76.0/22 with origin AS47063 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47063 in the RIR database for the space.672 of 673

Route objects not announced

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

38.109.123.0/24RADBNo ROA
162.219.76.0/22ARINValid

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.