bgpreport

Network · data from 2026-11-12

AS139994 XLSmart AS139994

Registry name: XLNET-FTTH-ID - PT XL Axiata Tbk, ID · PeeringDB

41IPv4 routes 97.6% RPKI valid · 90.2% with a route object
16IPv6 routes 100.0% RPKI valid · 93.8% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 5 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS139994, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS139994, 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.
140.213.189.0/24 Invalid: origin Other origin only 36 5%low visibility 23
103.3.222.0/24 Valid None 669 99% 67
103.3.220.0/24 Valid None 668 99% 67
103.3.221.0/24 Valid None 668 99% 67
2400:9800:6073::/48 Valid None 630 99% 68
157.85.209.0/24 Valid RIR databaseAPNIC 670 100% 67
140.213.1.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.3.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.8.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.10.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.12.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.118.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.186.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.187.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.188.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.190.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.200.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.201.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.202.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.203.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.210.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.216.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.217.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.197.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.198.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.203.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.204.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.205.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.206.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.207.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.208.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.210.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.211.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.212.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.213.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.218.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.219.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.220.0/24 Valid RIR databaseAPNIC 669 99% 67
157.85.221.0/24 Valid RIR databaseAPNIC 669 99% 67
140.213.94.0/24 Valid RIR databaseAPNIC 668 99% 67
140.213.95.0/24 Valid RIR databaseAPNIC 668 99% 67
157.85.202.0/24 Valid RIR databaseAPNIC 668 99% 67
2400:9800:6030::/47 Valid RIR databaseAPNIC 634 100% 70
2400:9800:6032::/47 Valid RIR databaseAPNIC 634 100% 70
2400:9800:6034::/47 Valid RIR databaseAPNIC 634 100% 70
2400:9800:6036::/47 Valid RIR databaseAPNIC 634 100% 70
2400:9800:6040::/47 Valid RIR databaseAPNIC 634 100% 70
2400:9800:6042::/47 Valid RIR databaseAPNIC 634 100% 70
2400:9800:6050::/47 Valid RIR databaseAPNIC 634 100% 70
2400:9800:6052::/47 Valid RIR databaseAPNIC 634 100% 70
2400:9800:6060::/48 Valid RIR databaseAPNIC 634 100% 70
2400:9800:6061::/48 Valid RIR databaseAPNIC 634 100% 70
2400:9800:6065::/48 Valid RIR databaseAPNIC 634 100% 70
2400:9800:6066::/48 Valid RIR databaseAPNIC 634 100% 70
2400:9800:6070::/48 Valid RIR databaseAPNIC 630 99% 70
2400:9800:6074::/48 Valid RIR databaseAPNIC 630 99% 70
2400:9800:6077::/48 Valid RIR databaseAPNIC 630 99% 70

AS-SET

PeeringDB's irr_as_set for AS139994: AS139994:AS-XLNET-FTTH. 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 (AS139994 isn't in the set, or no route object for AS139994 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 objectsAS139994 in itNot covered
AS139994:AS-XLNET-FTTH In no IRR database read today.

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: origin1
  • Route object: none5
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: origin140.213.189.0/24ROAs covering it name AS17885, AS24203, not AS139994. If AS139994 should announce it, add a ROA for AS139994.36 of 673
Route object: none140.213.189.0/24Route objects for it name AS17885. Add a route object with origin AS139994 in the RIR database for the space.36 of 673
Route object: none103.3.222.0/24No route object for it. Add a route object with origin AS139994 in the RIR database for the space.669 of 673
Route object: none103.3.220.0/24No route object for it. Add a route object with origin AS139994 in the RIR database for the space.668 of 673
Route object: none103.3.221.0/24No route object for it. Add a route object with origin AS139994 in the RIR database for the space.668 of 673
Route object: none2400:9800:6073::/48No route object for it. Add a route object with origin AS139994 in the RIR database for the space.630 of 636
AS-SET: not foundAS139994:AS-XLNET-FTTHPeeringDB names AS139994:AS-XLNET-FTTH; no IRR database read has it.

Route objects not announced

Every route object with origin AS139994 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.