bgpreport

Network · data from 2026-11-12

AS59455 Clearstream Technology Ltd

Registry name: CSG-AS Clearstream Technology ltd, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59455, 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.
2a06:9801:21a::/48 No ROA RIR databaseRIPE 635 100% 67
194.26.198.0/24 Valid Other origin only 673 100% 66
46.17.208.0/21 Valid RIR databaseRIPE 673 100% 66
185.23.52.0/22 Valid RIR databaseRIPE 673 100% 66
185.33.192.0/22 Valid RIR databaseRIPE 673 100% 66
185.79.108.0/23 Valid RIR databaseRIPE 673 100% 66
193.33.116.0/23 Valid RIR databaseRIPE 673 100% 66
193.111.33.0/24 Valid RIR databaseRIPE 673 100% 66
222.167.193.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
2a04:2340::/29 Valid RIR databaseRIPE 634 100% 67
2a13:9500:18a::/48 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS59455: AS-CSG. 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 (AS59455 isn't in the set, or no route object for AS59455 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 objectsAS59455 in itNot covered
AS-CSG RIPE 8124 Yes 1

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

  • ROA: none1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a06:9801:21a::/48No ROA covers it. Add a ROA for AS59455, maxLength 48.635 of 636
Route object: none194.26.198.0/24Route objects for it name AS206530. Add a route object with origin AS59455 in the RIR database for the space.673 of 673

Route objects not announced

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

185.98.108.0/22RIPENo 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.