Network · data from 2026-11-12

AS204104 Giti Secure Cloud

Registry name: GSC Giti Secure Cloud LLC, IR · PeeringDB

36IPv4 routes 97.2% RPKI valid · 91.7% with a route object

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

1RPKI invalid 1 origin · 0 maxLength

0No ROA 3 with no route object for this origin

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

9Route objects not announced registered with origin AS204104, seen from no peer

Announced routes

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


94.183.180.0/24	Invalid: origin	Other origin only	1 0%low visibility	1
87.107.170.0/24	Valid	Other origin only	672 100%	66
94.182.228.0/24	Valid	Other origin only	3 0%low visibility	2
31.56.17.0/24	Valid	RIR databaseRIPE	672 100%	66
31.56.89.0/24	Valid	RIR databaseRIPE	672 100%	66
31.57.21.0/24	Valid	RIR databaseRIPE	672 100%	66
31.58.237.0/24	Valid	RIR databaseRIPE	672 100%	66
46.38.143.0/24	Valid	RIR databaseRIPE	672 100%	66
62.220.120.0/24	Valid	RIR databaseRIPE	672 100%	66
87.107.115.0/24	Valid	RIR databaseRIPE	672 100%	66
87.107.194.0/24	Valid	RIR databaseRIPE	672 100%	66
87.107.207.0/24	Valid	RIR databaseRIPE	672 100%	66
92.42.207.0/24	Valid	RIR databaseRIPE	672 100%	66
212.80.8.0/24	Valid	RIR databaseRIPE	672 100%	66
37.32.43.0/24	Valid	RIR databaseRIPE	671 100%	66
37.152.175.0/24	Valid	RIR databaseRIPE	671 100%	66
46.38.138.0/24	Valid	RIR databaseRIPE	671 100%	66
62.220.121.0/24	Valid	RIR databaseRIPE	671 100%	66
81.12.50.0/24	Valid	RIR databaseRIPE	671 100%	66
87.107.113.0/24	Valid	RIR databaseRIPE	671 100%	66
87.107.114.0/24	Valid	RIR databaseRIPE	671 100%	66
87.107.162.0/24	Valid	RIR databaseRIPE	671 100%	66
87.107.169.0/24	Valid	RIR databaseRIPE	671 100%	66
87.107.192.0/24	Valid	RIR databaseRIPE	671 100%	66
87.107.206.0/24	Valid	RIR databaseRIPE	671 100%	66
94.183.153.0/24	Valid	RIR databaseRIPE	671 100%	66
94.183.154.0/24	Valid	RIR databaseRIPE	671 100%	66
94.184.30.0/24	Valid	RIR databaseRIPE	671 100%	66
87.107.112.0/24	Valid	RIR databaseRIPE	670 100%	66
87.107.195.0/24	Valid	RIR databaseRIPE	670 100%	66
212.80.9.0/24	Valid	RIR databaseRIPE	670 100%	66
217.60.238.0/24	Valid	RIR databaseRIPE	670 100%	66
2a10:ed40:2::/48	Valid	RIR databaseRIPE	633 100%	67
2a10:ed40:4::/48	Valid	RIR databaseRIPE	633 100%	67
2a10:ed40:5::/48	Valid	RIR databaseRIPE	633 100%	68
2a10:ed40:9::/48	Valid	RIR databaseRIPE	633 100%	67
2a10:ed40:a::/48	Valid	RIR databaseRIPE	633 100%	69
2a10:ed40:b::/48	Valid	RIR databaseRIPE	633 100%	69
87.107.193.0/24	Valid	RIR databaseRIPE	2 0%low visibility	2
94.183.162.0/24	Valid	RIR databaseRIPE	1 0%low visibility	1
94.183.166.0/24	Valid	RIR databaseRIPE	1 0%low visibility	1
94.184.44.0/24	Valid	RIR databaseRIPE	1 0%low visibility	1

94.183.180.0/24

Invalid: origin

Other origin only

1 0%low visibility

87.107.170.0/24

Valid

Other origin only

672 100%

94.182.228.0/24

Valid

Other origin only

3 0%low visibility

31.56.17.0/24

Valid

RIR databaseRIPE

672 100%

31.56.89.0/24

Valid

RIR databaseRIPE

672 100%

31.57.21.0/24

Valid

RIR databaseRIPE

672 100%

31.58.237.0/24

Valid

RIR databaseRIPE

672 100%

46.38.143.0/24

Valid

RIR databaseRIPE

672 100%

62.220.120.0/24

Valid

RIR databaseRIPE

672 100%

87.107.115.0/24

Valid

RIR databaseRIPE

672 100%

87.107.194.0/24

Valid

RIR databaseRIPE

672 100%

87.107.207.0/24

Valid

RIR databaseRIPE

672 100%

92.42.207.0/24

Valid

RIR databaseRIPE

672 100%

212.80.8.0/24

Valid

RIR databaseRIPE

672 100%

37.32.43.0/24

Valid

RIR databaseRIPE

671 100%

37.152.175.0/24

Valid

RIR databaseRIPE

671 100%

46.38.138.0/24

Valid

RIR databaseRIPE

671 100%

62.220.121.0/24

Valid

RIR databaseRIPE

671 100%

81.12.50.0/24

Valid

RIR databaseRIPE

671 100%

87.107.113.0/24

Valid

RIR databaseRIPE

671 100%

87.107.114.0/24

Valid

RIR databaseRIPE

671 100%

87.107.162.0/24

Valid

RIR databaseRIPE

671 100%

87.107.169.0/24

Valid

RIR databaseRIPE

671 100%

87.107.192.0/24

Valid

RIR databaseRIPE

671 100%

87.107.206.0/24

Valid

RIR databaseRIPE

671 100%

94.183.153.0/24

Valid

RIR databaseRIPE

671 100%

94.183.154.0/24

Valid

RIR databaseRIPE

671 100%

94.184.30.0/24

Valid

RIR databaseRIPE

671 100%

87.107.112.0/24

Valid

RIR databaseRIPE

670 100%

87.107.195.0/24

Valid

RIR databaseRIPE

670 100%

212.80.9.0/24

Valid

RIR databaseRIPE

670 100%

217.60.238.0/24

Valid

RIR databaseRIPE

670 100%

2a10:ed40:2::/48

Valid

RIR databaseRIPE

633 100%

2a10:ed40:4::/48

Valid

RIR databaseRIPE

633 100%

2a10:ed40:5::/48

Valid

RIR databaseRIPE

633 100%

2a10:ed40:9::/48

Valid

RIR databaseRIPE

633 100%

2a10:ed40:a::/48

Valid

RIR databaseRIPE

633 100%

2a10:ed40:b::/48

Valid

RIR databaseRIPE

633 100%

87.107.193.0/24

Valid

RIR databaseRIPE

2 0%low visibility

94.183.162.0/24

Valid

RIR databaseRIPE

1 0%low visibility

94.183.166.0/24

Valid

RIR databaseRIPE

1 0%low visibility

94.184.44.0/24

Valid

RIR databaseRIPE

1 0%low visibility

AS-SET

AS204104's PeeringDB record names no 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: origin1
Route object: none3
Route object: not announced9

Change	Prefix or set	Detail	Full-table peers
ROA: origin	94.183.180.0/24	ROAs covering it name AS216169, not AS204104. If AS204104 should announce it, add a ROA for AS204104.	1 of 673
Route object: none	94.183.180.0/24	Route objects for it name AS216169. Add a route object with origin AS204104 in the RIR database for the space.	1 of 673
Route object: none	87.107.170.0/24	Route objects for it name AS214957. Add a route object with origin AS204104 in the RIR database for the space.	672 of 673
Route object: none	94.182.228.0/24	Route objects for it name AS31549. Add a route object with origin AS204104 in the RIR database for the space.	3 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

94.183.180.0/24

ROAs covering it name AS216169, not AS204104. If AS204104 should announce it, add a ROA for AS204104.

1 of 673

Route object: none

94.183.180.0/24

Route objects for it name AS216169. Add a route object with origin AS204104 in the RIR database for the space.

1 of 673

Route object: none

87.107.170.0/24

Route objects for it name AS214957. Add a route object with origin AS204104 in the RIR database for the space.

672 of 673

Route object: none

94.182.228.0/24

Route objects for it name AS31549. Add a route object with origin AS204104 in the RIR database for the space.

3 of 673

Route objects not announced

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


62.220.110.0/24	RIPE	Valid
62.220.111.0/24	RIPE	Valid
85.133.166.0/24	RIPE	Invalid: origin
87.107.163.0/24	RIPE	Valid
94.183.150.0/24	RIPE	Valid
185.212.49.0/24	RIPE	Valid
212.80.10.0/24	RIPE	Valid
2a10:ed40::/48	RIPE	Valid
2a10:ed40:1::/48	RIPE	Valid

62.220.110.0/24

RIPE

Valid

62.220.111.0/24

RIPE

Valid

85.133.166.0/24

RIPE

Invalid: origin

87.107.163.0/24

RIPE

Valid

94.183.150.0/24

RIPE

Valid

185.212.49.0/24

RIPE

Valid

212.80.10.0/24

RIPE

Valid

2a10:ed40::/48

RIPE

Valid

2a10:ed40:1::/48

RIPE

Valid

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.