Network · data from 2026-11-12

AS213473 kalaam-KSA

Registry name: kalaam-KSA Kalaam Telecom for Communications LLC, SA · PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

0Route objects not announced registered with origin AS213473, seen from no peer

Announced routes

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


77.83.88.0/22	Valid	RIR databaseRIPE	673 100%	66
77.92.160.0/21	Valid	RIR databaseRIPE	673 100%	66
77.92.180.0/22	Valid	RIR databaseRIPE	673 100%	66
91.220.94.0/24	Valid	RIR databaseRIPE	673 100%	66
185.225.56.0/22	Valid	RIR databaseRIPE	673 100%	66
185.225.56.0/24	Valid	RIR databaseRIPE	673 100%	66
185.225.57.0/24	Valid	RIR databaseRIPE	673 100%	66
185.225.58.0/24	Valid	RIR databaseRIPE	673 100%	67
185.225.59.0/24	Valid	RIR databaseRIPE	673 100%	66
77.83.88.0/24	Valid	RIR databaseRIPE	672 100%	66
77.83.89.0/24	Valid	RIR databaseRIPE	672 100%	66
77.83.90.0/24	Valid	RIR databaseRIPE	672 100%	66
77.83.91.0/24	Valid	RIR databaseRIPE	672 100%	66
77.92.160.0/24	Valid	RIR databaseRIPE	672 100%	66
77.92.162.0/24	Valid	RIR databaseRIPE	672 100%	66
77.92.163.0/24	Valid	RIR databaseRIPE	672 100%	66
77.92.164.0/24	Valid	RIR databaseRIPE	672 100%	66
77.92.165.0/24	Valid	RIR databaseRIPE	672 100%	66
77.92.166.0/24	Valid	RIR databaseRIPE	672 100%	66
77.92.167.0/24	Valid	RIR databaseRIPE	672 100%	67
77.92.180.0/24	Valid	RIR databaseRIPE	672 100%	66
77.92.181.0/24	Valid	RIR databaseRIPE	672 100%	66
77.92.182.0/24	Valid	RIR databaseRIPE	672 100%	66
77.92.183.0/24	Valid	RIR databaseRIPE	672 100%	66
77.92.161.0/24	Valid	RIR databaseRIPE	671 100%	66
2a14:e500::/29	Valid	RIR databaseRIPE	635 100%	69
2a14:e504::/30	Valid	RIR databaseRIPE	635 100%	69
2a14:e500::/30	Valid	RIR databaseRIPE	633 100%	68

AS-SET

PeeringDB's irr_as_set for AS213473: AS213473:AS-KALAAM. 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 (AS213473 isn't in the set, or no route object for AS213473 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	AS213473 in it	Not covered
AS213473:AS-KALAAM	RIPE	0	1	0	No	28

Name

Database

ASNs

Sets

Route objects

AS213473 in it

Not covered

AS213473:AS-KALAAM

RIPE

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

AS-SET: own ASN1

Change	Prefix or set	Detail	Full-table peers
AS-SET: own ASN	AS213473:AS-KALAAM	AS213473 isn't in AS213473:AS-KALAAM (RIPE) once expanded. Add AS213473 to it.

Change

Prefix or set

Detail

Full-table peers

AS-SET: own ASN

AS213473:AS-KALAAM

AS213473 isn't in AS213473:AS-KALAAM (RIPE) once expanded. Add AS213473 to it.

Route objects not announced

Every route object with origin AS213473 is announced.

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.