Autonomous system detail

AS203

Announced

Operated by CENTURYLINK-LEGACY-LVLT-203 - Level 3 Parent, LLC.

Summary

// analyst note
Actively-routed legacy stub. Stub topology (1 upstream, 0 peers, 0 customers) double-confirmed by CAIDA AS Rank and RIPEstat. Upstream identity AS3356 is from operator/community sources, not canonical degree data (tagged Likely). The 2020 routing incident is well-sourced but attribution remains open.
// security note
DATED: one documented routing incident on 2020-10-21 (AS203 announced 158 prefixes it was not origin for; 1,100+ conflicts; 31 ISPs in 19 countries; reported on NANOG, analyzed by Qrator).
IPv4 prefixes
125
~180.2K addresses
IPv6 prefixes
1
announced
Peer networks
1
1 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: High

AS203 is a legacy autonomous system number registered under ARIN to Level 3 Parent, LLC, the corporate entity preserved in ARIN records after CenturyLink acquired Level 3 Communications in 2017 and later rebranded as Lumen Technologies. The ARIN name CENTURYLINK-LEGACY-LVLT-203 reflects that acquisition history, with the LVLT token echoing Level 3's former NASDAQ ticker. Unlike Merit's dormant AS181, AS203 is actively routed but functions as a pure customer stub: CAIDA reports a total degree of 1 (one upstream provider, zero peers, zero customers), and RIPEstat observes a single BGP neighbour. It originates roughly 122 IPv4 prefixes (about 174,592 addresses) and a single IPv6 prefix; the Lumen/Level 3 go-forward backbone is AS3356, not AS203, so this number carries residual legacy address space rather than primary operations. The one notable security event in the public record is an October 2020 routing incident, reported on NANOG and analyzed by Qrator, in which AS203 announced 158 prefixes it was not the legitimate origin for, generating over 1,100 routing conflicts across 31 ISPs in 19 countries; the root cause (Lumen misconfiguration versus external exploitation of missing prefix filters) was never publicly confirmed, and Lumen closed its internal ticket as no-fault. RPKI coverage on this block is poor, with roughly 80 prefixes carrying IRR origin-mismatch flags. No spam or malware blacklist presence was confirmed for AS203 specifically as of 2026-06-19, though several feeds could not be queried directly.

Operator
Level 3 Parent, LLC (subsidiary of Lumen Technologies, NYSE: LUMN; formerly CenturyLink/Level 3) [Confirmed] — ARIN RDAP, lumen.com/en-us/about.html
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP autnum/203
Allocated
2002-06-05 (ARIN registry date from autnum top-level registration event, NOT an IEEE date — IEEE publishes no ASN dates); last changed 2019-12-04 [Confirmed] — ARIN RDAP autnum top-level events (two angles: A2, A3)
Org status
active corporate entity; Level 3 Parent, LLC preserved in ARIN records, subsidiary of Lumen Technologies Inc (HQ Broomfield, CO) [Confirmed] — ARIN RDAP, en.wikipedia.org/wiki/Lumen_Technologies
Contacts
abuse@level3.com (also abuse@aup.lumen.com); admin ipadmin@lumen.com / ipadmin@centurylink.com; looking glass lookingglass.centurylink.com; registered address 100 CenturyLink Drive, Monroe, LA 71203 [Confirmed] — ARIN RDAP entities (LAC56-ARIN, APL7-ARIN)

Security/abuse context (DATED)

one documented routing incident on 2020-10-21 — AS203 announced 158 prefixes it was not origin for, 1,100+ conflicts, 31 ISPs / 19 countries; root cause (misconfig vs. hijack) unconfirmed, Lumen claimed no fault. Academic AP2Vec (IEEE 2022) flagged a similar AS203 anomaly. No confirmed spam/malware blacklist presence as of 2026-06-19 (some feeds returned 403 and could not be queried) [Confirmed for the 2020 incident; Unknown for blacklist status due to feed access limits] — seclists.org/nanog/2020/Oct/314, blog.qrator.net, radar.qrator.net/as203, ieeexplore.ieee.org/document/9754706/

Network & routing

Network type
legacy stub AS within the Lumen/Level 3 Tier 1 estate; carries residual Level 3 IPv4 space, not the primary operational ASN [Confirmed] — ipinfo.io/AS203, bgp.he.net/AS203
Size
~122 IPv4 prefixes / ~174,592 IPv4 addresses; 1 IPv6 prefix (example 2804:cf4::/32). Source ranges vary (bgp.he.net ~123, ip2location ~130) [Confirmed for RIPEstat counts; Likely for the cross-source range] — RIPEstat routing-status, bgp.he.net, ipinfo.io
Routing/topology
pure customer stub — CAIDA degree total 1 (provider 1, customer 0, peer 0); RIPEstat observes 1 BGP neighbour. Sole upstream is AS3356 (Level 3 Parent, LLC itself) [Confirmed for stub topology via A3 CAIDA + RIPEstat; AS3356 upstream Likely — A2 names it, canonical CAIDA returns degree only]
Peering policy
no independent AS203 policy (not a standalone PeeringDB entry); the parent Lumen policy is Selective with high thresholds (e.g. 500 Gbps / 1,000 ASNs global, RPKI filtering) and discretionary [Confirmed for org policy; AS203 itself not separately listed] — lumen.com/en-us/about/legal/peering-policy.html, peeringdb.com/org/682
RPKI
poor coverage — ~80 prefixes flagged IRR "Parent Route Origin Mismatch"; RPKI-ROA contact RPKIR-ARIN registered 2024-06-17 (rpki-roa@lumen.com) indicates active ROA operations but incomplete validity on this block [Likely] — bgp.tools/as/203, bgp.he.net/AS203, ARIN RDAP entity/RPKIR-ARIN
Notable usage
legacy Level 3 Communications block pre-dating the 2017 CenturyLink acquisition; Level 3 was historically a major Tier 1 backbone and CDN transit carrier. Go-forward Lumen internet platform is AS3356 — en.wikipedia.org/wiki/Level_3_Communications, bgp.he.net/AS203
Related ASNs
AS3356 (Lumen/Level 3 primary backbone and AS203's upstream) [Confirmed for relationship; identity of upstream Likely per A2]
ARIN name / org handle
CENTURYLINK-LEGACY-LVLT-203 / org LPL-141 [Confirmed] — ARIN RDAP autnum/203
Visibility
full RIS v4 visibility (327/327 peers); minimal v6 (15/323 peers); CAIDA rank 13,154; customer cone 1 ASN / 128 prefixes / ~116,320 addresses [Confirmed] — RIPEstat routing-status, CAIDA AS Rank
Analyst note
actively-routed legacy stub. Topology facts (stub, 1 upstream) are double-confirmed by CAIDA and RIPEstat; the upstream's identity as AS3356 is from operator/community sources, not the canonical degree data, so tagged Likely. The 2020 incident is well-sourced but attribution stays open.
[ 02 ] — Announced prefixes

What this network routes.

126 prefixes total · RIPEstat data · cached, not real-time
// IPv4 prefixes125
  1. 170.46.0.0/16/16
  2. 156.42.32.0/19/19
  3. 156.42.160.0/19/19
  4. 156.42.224.0/19/19
  5. 161.209.192.0/19/19
  6. 156.42.64.0/19/19
  7. 156.42.96.0/19/19
  8. 156.42.128.0/19/19
  9. 156.42.192.0/19/19
  10. 156.42.0.0/19/19
  11. 161.209.96.0/20/20
  12. 216.235.200.0/21/21
  13. 63.128.0.0/22/22
  14. 209.67.136.0/22/22
  15. 209.67.132.0/22/22
  16. 205.139.104.0/22/22
  17. 63.128.8.0/22/22
  18. 143.199.140.0/23/23
  19. 65.240.184.0/23/23
  20. 170.46.132.0/23/23
  21. 204.153.154.0/23/23
  22. 205.140.220.0/23/23
  23. 63.150.74.0/23/23
  24. 205.139.32.0/23/23
  25. 165.193.54.0/23/23
  26. 209.164.193.0/24/24
  27. 143.199.109.0/24/24
  28. 209.164.205.0/24/24
  29. 209.164.194.0/24/24
  30. 205.139.108.0/24/24
  31. 216.163.254.0/24/24
  32. 205.140.226.0/24/24
  33. 170.46.155.0/24/24
  34. 63.106.6.0/24/24
  35. 161.209.97.0/24/24
  36. 216.32.151.0/24/24
  37. 216.163.251.0/24/24
  38. 143.199.96.0/24/24
  39. 216.163.253.0/24/24
  40. 204.164.72.0/24/24
  41. 170.46.150.0/24/24
  42. 64.241.120.0/24/24
  43. 216.163.246.0/24/24
  44. 192.26.214.0/24/24
  45. 205.166.171.0/24/24
  46. 148.59.169.0/24/24
  47. 161.209.111.0/24/24
  48. 170.46.10.0/24/24
  49. 209.164.220.0/24/24
  50. 216.163.241.0/24/24
  51. 216.163.244.0/24/24
  52. 63.128.14.0/24/24
  53. 216.163.249.0/24/24
  54. 161.209.103.0/24/24
  55. 161.209.102.0/24/24
  56. 8.44.205.0/24/24
  57. 161.209.99.0/24/24
  58. 66.193.107.0/24/24
  59. 192.42.110.0/24/24
  60. 64.209.141.0/24/24
  61. 50.58.252.0/24/24
  62. 216.163.255.0/24/24
  63. 63.128.1.0/24/24
  64. 209.164.223.0/24/24
  65. 62.67.222.0/24/24
  66. 63.128.20.0/24/24
  67. 216.163.247.0/24/24
  68. 64.22.148.0/24/24
  69. 209.164.211.0/24/24
  70. 206.169.67.0/24/24
  71. 216.163.243.0/24/24
  72. 216.163.248.0/24/24
  73. 161.209.96.0/24/24
  74. 64.241.121.0/24/24
  75. 209.164.195.0/24/24
  76. 209.164.207.0/24/24
  77. 209.164.204.0/24/24
  78. 209.164.192.0/24/24
  79. 38.107.240.0/24/24
  80. 216.163.240.0/24/24
  81. 170.22.90.0/24/24
  82. 216.163.252.0/24/24
  83. 161.209.98.0/24/24
  84. 143.199.145.0/24/24
  85. 198.135.250.0/24/24
  86. 8.20.69.0/24/24
  87. 205.139.102.0/24/24
  88. 158.120.127.0/24/24
  89. 198.200.148.0/24/24
  90. 128.177.179.0/24/24
  91. 216.163.242.0/24/24
  92. 216.33.160.0/24/24
  93. 209.164.221.0/24/24
  94. 66.194.187.0/24/24
  95. 205.139.103.0/24/24
  96. 170.46.162.0/24/24
  97. 63.128.7.0/24/24
  98. 161.209.101.0/24/24
  99. 64.210.246.0/24/24
  100. 206.79.6.0/24/24
  101. 63.128.24.0/24/24
  102. 8.18.63.0/24/24
  103. 8.7.155.0/24/24
  104. 63.144.218.0/24/24
  105. 63.128.12.0/24/24
  106. 148.59.168.0/24/24
  107. 8.25.26.0/24/24
  108. 189.125.51.0/24/24
  109. 65.222.131.0/24/24
  110. 216.163.250.0/24/24
  111. 204.17.219.0/24/24
  112. 216.163.245.0/24/24
  113. 204.146.159.0/24/24
  114. 64.208.127.0/24/24
  115. 170.46.200.0/24/24
  116. 192.147.2.0/24/24
  117. 143.199.28.0/24/24
  118. 209.164.208.0/24/24
  119. 143.199.222.0/24/24
  120. 209.164.209.0/24/24
  121. 161.209.100.0/24/24
  122. 143.199.135.0/24/24
  123. 161.209.225.0/24/24
  124. 8.15.229.0/24/24
  125. 216.114.73.0/24/24
// IPv6 prefixes1
  1. 2804:cf4::/32/32
[ 03 ] — Notable peers & upstreams

Who it talks to.

1 observed neighbour
// Notable connectionsTop 1 of 1
ASNOperatorRole
AS3356 LEVEL3 - Level 3 Parent, LLC upstream
Neighbours observed via public BGP collectors; not a complete peering list.