bgpreport

Network · data from 2026-11-12

AS45489 Sri Lanka Telecom Global

Registry name: SLT-GLOBAL - Sri Lanka Telecom PLC, GLobal Peering, LK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45489, 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.
192.168.255.0/24 bogon No ROA None 1 0%low visibility 1
::/0 bogon No ROA None 1 0%low visibility 2
103.87.124.0/23 Valid RIR databaseAPNIC, RADB 672 100% 66
203.96.163.0/24 Valid RIR databaseAPNIC 672 100% 66
2001:df4:1b00::/48 Valid RIR databaseAPNIC, RADB 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS45489: RADB::AS-SLT-GLOBAL. 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 (AS45489 isn't in the set, or no route object for AS45489 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 objectsAS45489 in itNot covered
RADB::AS-SLT-GLOBAL RADB1 member set in no database: AS-137956 160155,945 Yes 2

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

  • Bogon prefix2
  • AS-SET: missing member1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Bogon prefix192.168.255.0/24In IANA's special-purpose registry: Private-Use (RFC 1918).1 of 673
Bogon prefix::/0In IANA's special-purpose registry: default route.1 of 636
AS-SET: missing memberRADB::AS-SLT-GLOBALAS-SLT-GLOBAL (RADB) lists AS-137956; no IRR database read has it.

Route objects not announced

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

103.87.124.0/24APNIC, RADBValid
103.87.125.0/24APNIC, RADBValid

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.