Network · data from 2026-11-12

AS57388 I.B.C-TELECOM

Registry name: IBC-AS I.B.C - Telecom Sh.p.k., AL · PeeringDB

14IPv4 routes 100.0% RPKI valid · 92.9% with a route object

4IPv6 routes 100.0% RPKI valid · 100.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

3Route objects not announced registered with origin AS57388, seen from no peer

Announced routes

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


185.85.154.0/24	Valid	Nonecovered by 185.85.152.0/22	672 100%	67
130.0.28.0/24	Valid	RIR databaseRIPE	673 100%	67
130.0.29.0/24	Valid	RIR databaseRIPE	673 100%	67
130.0.24.0/21	Valid	RIR databaseRIPE	672 100%	67
130.0.24.0/24	Valid	RIR databaseRIPE	672 100%	67
130.0.25.0/24	Valid	RIR databaseRIPE	672 100%	67
130.0.26.0/24	Valid	RIR databaseRIPE	672 100%	67
130.0.27.0/24	Valid	RIR databaseRIPE	672 100%	67
130.0.30.0/24	Valid	RIR databaseRIPE	672 100%	67
130.0.31.0/24	Valid	RIR databaseRIPE	672 100%	67
157.173.38.0/24	Valid	RIR databaseRIPE	672 100%	67
185.85.152.0/22	Valid	RIR databaseRIPE	672 100%	67
185.85.155.0/24	Valid	RIR databaseRIPE	672 100%	67
185.139.4.0/24	Valid	RIR databaseRIPE	672 100%	67
2a02:dd00:1a::/48	Valid	RIR databaseRIPE	628 99%	67
2a02:dd00:1b::/48	Valid	RIR databaseRIPE	628 99%	67
2a02:dd01:9ff0::/48	Valid	RIR databaseRIPE	628 99%	67
2a02:dd00::/29	Valid	RIR databaseRIPE	627 99%	67

AS-SET

PeeringDB's irr_as_set for AS57388: AS57388:AS-IBC-SET. 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 (AS57388 isn't in the set, or no route object for AS57388 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.

Name	Database	ASNs	Sets	Route objects	AS57388 in it	Not covered
AS57388:AS-IBC-SET	RIPE	43	5	57,211	Yes	0

Name

Database

ASNs

Sets

Route objects

AS57388 in it

Not covered

AS57388:AS-IBC-SET

RIPE

57,211

Yes

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

Route object: none1
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
Route object: none	185.85.154.0/24	No route object for it. A route object for 185.85.152.0/22 with origin AS57388 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57388 in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

185.85.154.0/24

No route object for it. A route object for 185.85.152.0/22 with origin AS57388 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57388 in the RIR database for the space.

672 of 673

Route objects not announced

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


185.85.152.0/23	RIPE	Valid
2a02:dd00::/48	RIPE	Valid
2a02:dd00::/50	RIPE	Invalid: maxLength

185.85.152.0/23

RIPE

Valid

2a02:dd00::/48

RIPE

Valid

2a02:dd00::/50

RIPE

Invalid: maxLength

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.