bgpreport

Network · data from 2026-11-12

AS138934 SLTNetworkCoLTD-AS-AP - SLT Network Co.,LTD

Registry name: SLTNetworkCoLTD-AS-AP - SLT Network Co.,LTD, LA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS138934, 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:adc0::/48 Invalid: maxLength Nonecovered by 2404:adc0::/32 10 2%low visibility 7
2404:adc0:1::/48 Invalid: maxLength Nonecovered by 2404:adc0::/32 10 2%low visibility 7
103.137.88.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.137.88.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.137.89.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.137.90.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.137.91.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68

AS-SET

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

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength2404:adc0::/48ROA 2404:adc0::/32 AS138934 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2404:adc0::/48.10 of 636
Route object: none2404:adc0::/48No route object for it. A route object for 2404:adc0::/32 with origin AS138934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138934 in the RIR database for the space.10 of 636
ROA: maxLength2404:adc0:1::/48ROA 2404:adc0::/32 AS138934 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2404:adc0:1::/48.10 of 636
Route object: none2404:adc0:1::/48No route object for it. A route object for 2404:adc0::/32 with origin AS138934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138934 in the RIR database for the space.10 of 636

Route objects not announced

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

103.137.88.0/23APNIC, NTTCOM, RADBValid
103.137.90.0/23APNIC, NTTCOM, RADBValid
2404:adc0::/32APNIC, 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.