Network · data from 2026-11-12

AS207249 ICS Icard Services EAD

Registry name: ICS Icard Services EAD, BG · not in PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

15Route objects not announced registered with origin AS207249, seen from no peer

Announced routes

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


2a05:1602::/32	Valid	Other origin onlycovered by 2a05:1600::/29	635 100%	69
185.161.232.0/24	Valid	RIR databaseRIPE	673 100%	66
185.161.233.0/24	Valid	RIR databaseRIPE	671 100%	68
185.161.234.0/24	Valid	RIR databaseRIPE	671 100%	68
185.161.235.0/24	Valid	RIR databaseRIPE	671 100%	68
185.68.46.0/24	Valid	RIR databaseRIPE	666 99%	68
185.68.47.0/24	Valid	RIR databaseRIPE	666 99%	68
2a07:c884::/32	Valid	RIR databaseRIPE	634 100%	70

AS-SET

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

Route object: none1
Route object: not announced15

Change	Prefix or set	Detail	Full-table peers
Route object: none	2a05:1602::/32	Route objects for it name AS59872. A route object for 2a05:1600::/29 with origin AS207249 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207249 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2a05:1602::/32

Route objects for it name AS59872. A route object for 2a05:1600::/29 with origin AS207249 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207249 in the RIR database for the space.

635 of 636

Route objects not announced

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


91.206.20.0/23	RIPE	Valid
91.206.20.0/24	RIPE	Valid
185.68.44.0/22	RIPE	Valid
185.68.44.0/24	RIPE	Valid
185.68.45.0/24	RIPE	Invalid: maxLength
185.161.232.0/22	RIPE	Valid
185.161.232.0/23	RIPE	Valid
185.161.234.0/23	RIPE	Valid
2a05:1600::/29	RIPE	Valid
2a07:c880::/29	RIPE	Valid
2a07:c880::/32	RIPE	Valid
2a07:c881::/32	RIPE	Valid
2a07:c882::/32	RIPE	Valid
2a07:c883::/32	RIPE	Valid
2a07:c885::/32	RIPE	Valid

91.206.20.0/23

RIPE

Valid

91.206.20.0/24

RIPE

Valid

185.68.44.0/22

RIPE

Valid

185.68.44.0/24

RIPE

Valid

185.68.45.0/24

RIPE

Invalid: maxLength

185.161.232.0/22

RIPE

Valid

185.161.232.0/23

RIPE

Valid

185.161.234.0/23

RIPE

Valid

2a05:1600::/29

RIPE

Valid

2a07:c880::/29

RIPE

Valid

2a07:c880::/32

RIPE

Valid

2a07:c881::/32

RIPE

Valid

2a07:c882::/32

RIPE

Valid

2a07:c883::/32

RIPE

Valid

2a07:c885::/32

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.