Network · data from 2026-11-12

AS58655 SkyTel Communications Limited

Registry name: SKYTEL6-BD - SkyTel Communications Limited, BD · PeeringDB

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

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

1RPKI invalid 0 origin · 1 maxLength

0No 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 AS58655, seen from no peer

Announced routes

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


2404:7500:8::/48	Invalid: maxLength	Nonecovered by 2404:7500::/32	101 16%	43
103.12.172.0/22	Valid	RIR databaseAPNIC	673 100%	66
103.12.172.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.12.175.0/24	Valid	RIR databaseAPNIC	673 100%	67
220.152.112.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.12.173.0/24	Valid	RIR databaseAPNIC	670 100%	68
103.12.174.0/24	Valid	RIR databaseAPNIC	670 100%	68
151.158.216.0/24	Valid	RIR databaseAPNIC	670 100%	68
182.252.94.0/24	Valid	RIR databaseAPNIC	670 100%	68
182.252.95.0/24	Valid	RIR databaseAPNIC	670 100%	68
2404:7500::/32	Valid	RIR databaseAPNIC	636 100%	70
2404:7500::/48	Valid	RIR databaseAPNIC	635 100%	70

AS-SET

PeeringDB's irr_as_set for AS58655: AS58655:AS-SKYTEL6-BD. 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 (AS58655 isn't in the set, or no route object for AS58655 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	AS58655 in it	Not covered
AS58655:AS-SKYTEL6-BD	APNIC	299	5	27,184	Yes	0

Name

Database

ASNs

Sets

Route objects

AS58655 in it

Not covered

AS58655:AS-SKYTEL6-BD

APNIC

299

27,184

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

ROA: maxLength1
Route object: none1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	2404:7500:8::/48	ROA 2404:7500::/32 AS58655 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2404:7500:8::/48.	101 of 636
Route object: none	2404:7500:8::/48	No route object for it. A route object for 2404:7500::/32 with origin AS58655 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58655 in the RIR database for the space.	101 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

2404:7500:8::/48

ROA 2404:7500::/32 AS58655 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2404:7500:8::/48.

101 of 636

Route object: none

2404:7500:8::/48

No route object for it. A route object for 2404:7500::/32 with origin AS58655 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58655 in the RIR database for the space.

101 of 636

Route objects not announced

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


182.252.94.0/23	APNIC	Valid

182.252.94.0/23

APNIC

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.