Network · data from 2026-11-12

AS201471 BIGSTEP-CLOUD Bigstep Cloud Limited

Registry name: BIGSTEP-CLOUD Bigstep Cloud Limited, GB · not in PeeringDB

11IPv4 routes 90.9% RPKI valid · 100.0% with a route object

2IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

11Route objects not announced registered with origin AS201471, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201471, 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.


66.232.128.0/21	No ROA	Other IRR onlyRADB	671 100%	67
84.40.0.0/20	Valid	RIR databaseRIPE	671 100%	67
84.40.32.0/21	Valid	RIR databaseRIPE	671 100%	67
84.40.40.0/21	Valid	RIR databaseRIPE	671 100%	67
84.40.58.0/23	Valid	RIR databaseRIPE	671 100%	67
84.40.60.0/22	Valid	RIR databaseRIPE	671 100%	67
176.223.248.0/23	Valid	RIR databaseRADB, RIPE	671 100%	68
176.223.249.0/24	Valid	RIR databaseRIPE	671 100%	67
176.223.250.0/23	Valid	RIR databaseRIPE	671 100%	68
176.223.251.0/24	Valid	RIR databaseRIPE	671 100%	68
185.90.48.0/22	Valid	RIR databaseRIPE	671 100%	67
2a02:cb8::/41	Valid	RIR databaseRIPE	634 100%	68
2001:67c:4dc::/48	Valid	RIR databaseRIPE	633 100%	67

AS-SET

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

ROA: none1
Route object: RIR1
Route object: not announced11

Change	Prefix or set	Detail	Full-table peers
ROA: none	66.232.128.0/21	No ROA covers it. Add a ROA for AS201471, maxLength 21.	671 of 673
Route object: RIR	66.232.128.0/21	Route object only in RADB. Add it in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

66.232.128.0/21

No ROA covers it. Add a ROA for AS201471, maxLength 21.

671 of 673

Route object: RIR

66.232.128.0/21

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route objects not announced

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


84.40.12.0/24	RIPE	Valid
84.40.38.0/24	RIPE	Valid
84.40.56.0/24	RIPE	No ROA
176.223.244.0/22	RIPE	Invalid: origin
176.223.248.0/22	RIPE	No ROA
176.223.248.0/24	RIPE	Valid
176.223.250.0/24	RIPE	Valid
194.126.253.0/24	RIPE	Invalid: origin
2001:67c:2e24::/48	RIPE	No ROA
2a02:cb8::/29	RIPE	No ROA
2a02:cb8:80::/41	RIPE	No ROA

84.40.12.0/24

RIPE

Valid

84.40.38.0/24

RIPE

Valid

84.40.56.0/24

RIPE

No ROA

176.223.244.0/22

RIPE

Invalid: origin

176.223.248.0/22

RIPE

No ROA

176.223.248.0/24

RIPE

Valid

176.223.250.0/24

RIPE

Valid

194.126.253.0/24

RIPE

Invalid: origin

2001:67c:2e24::/48

RIPE

No ROA

2a02:cb8::/29

RIPE

No ROA

2a02:cb8:80::/41

RIPE

No ROA

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.