City: unknown
Region: unknown
Country: United States
Internet Service Provider: RTC Communications LLC
Hostname: unknown
Organization: unknown
Usage Type: unknown
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
NetRange: 206.129.0.0 - 206.129.255.255
CIDR: 206.129.0.0/16
NetName: CENTURYLINK-LEGACY-SAVIXA-NET3
NetHandle: NET-206-129-0-0-1
Parent: NET206 (NET-206-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: CenturyLink Communications, LLC (CCL-534)
RegDate: 1995-09-14
Updated: 2018-11-15
Ref: https://rdap.arin.net/registry/ip/206.129.0.0
OrgName: CenturyLink Communications, LLC
OrgId: CCL-534
Address: 100 CENTURYLINK DR
City: Monroe
StateProv: LA
PostalCode: 71201
Country: US
RegDate: 2018-07-12
Updated: 2024-06-17
Comment: USAGE OF IP SPACE MUST COMPLY WITH OUR ACCEPTABLE USE POLICY:
Comment: https://www.lumen.com/en-us/about/legal/acceptable-use-policy.html
Comment:
Comment: ADDRESSES COVERED BY THIS ORG-ID ARE NON-PORTABLE ANY ISP ANNOUNCING OR TRANSITING PORTIONS WITHIN OUR RANGES SHOULD NOT RELY ON PRESENTED LOA'S OR OLD WHOIS UNLESS THOSE RANGES ARE ALSO ACTIVELY DIRECTLY ANNOUNCED TO A LUMEN ASN. WITH ALL LOA'S THESE CONDITIONS APPLY:
Comment:
Comment: 1. You are permitted to route the Lumen IP prefixes listed via Public BGP to your alternate ISP from the designated ASN. Any other ASN originating the prefix listed is forbidden.
Comment: 2. The Lumen IP prefixes listed can be routed via Public BGP to your alternate ISP as long as you remain an active customer with Lumen and continue to route the prefixes over at least one Lumen Internet circuit without significant traffic engineering.
Comment: 3. Should your Internet services with Lumen be discontinued, Lumen reserves the right to have your alternate ISP terminate the routing of the Lumen IP prefixes without advanced notification, should you fail to do so.
Comment: 4. All IP Addresses assigned or allocated by Lumen to an end-user (customer or ISP) shall be considered non-portable and will be reclaimed by Lumen upon service termination.
Comment: 5. Lumen reserves the right to conduct audits to ensure the LOA conditions are being met.
Comment: 6. Usage of IP space must comply with our AUP https://www.lumen.com/en-us/about/legal/acceptable-use-policy.html
Comment:
Comment: Our looking glass is located at: https://lookingglass.centurylink.com/
Comment:
Comment: For subpoena or court order please fax 844.254.5800 or refer to our Trust & Safety page:
Comment: https://www.lumen.com/en-us/about/legal/trust-center/trust-and-safety.html
Comment:
Comment: For abuse issues, please email abuse@aup.lumen.com
Comment: All abuse reports MUST include:
Comment: * src IP
Comment: * dest IP (your IP)
Comment: * dest port
Comment: * Accurate date/timestamp and timezone of activity
Comment: * Intensity/frequency (short log extracts)
Comment: * Your contact details (phone and email)
Comment: Without these we will be unable to identify the correct owner of the IP address at that point in time.
Ref: https://rdap.arin.net/registry/entity/CCL-534
OrgTechHandle: QIA-ARIN
OrgTechName: Centurylink IP Admin
OrgTechPhone: +1-877-886-6515
OrgTechEmail: ipadmin@centurylink.com
OrgTechRef: https://rdap.arin.net/registry/entity/QIA-ARIN
OrgAbuseHandle: CAD54-ARIN
OrgAbuseName: Centurylink Abuse Desk
OrgAbusePhone: +1-877-886-6515
OrgAbuseEmail: abuse@aup.lumen.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/CAD54-ARIN
OrgRoutingHandle: RPKIR-ARIN
OrgRoutingName: RPKI-ROA
OrgRoutingPhone: +1-877-886-6515
OrgRoutingEmail: rpki-roa@lumen.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/RPKIR-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 206.129.156.201
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21571
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;206.129.156.201. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026031701 1800 900 604800 86400
;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 18 10:37:34 CST 2026
;; MSG SIZE rcvd: 108Host 201.156.129.206.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 201.156.129.206.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 187.194.1.220 | attackspam | Telnet Server BruteForce Attack |
2019-12-06 13:11:52 |
| 51.15.56.133 | attackbots | Dec 6 10:24:33 vibhu-HP-Z238-Microtower-Workstation sshd\[5251\]: Invalid user nologin from 51.15.56.133 Dec 6 10:24:33 vibhu-HP-Z238-Microtower-Workstation sshd\[5251\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.15.56.133 Dec 6 10:24:34 vibhu-HP-Z238-Microtower-Workstation sshd\[5251\]: Failed password for invalid user nologin from 51.15.56.133 port 48864 ssh2 Dec 6 10:29:48 vibhu-HP-Z238-Microtower-Workstation sshd\[5553\]: Invalid user engelsen from 51.15.56.133 Dec 6 10:29:48 vibhu-HP-Z238-Microtower-Workstation sshd\[5553\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.15.56.133 ... |
2019-12-06 13:09:24 |
| 149.56.46.220 | attack | $f2bV_matches |
2019-12-06 10:06:52 |
| 109.250.150.110 | attack | Dec 6 06:00:00 [host] sshd[22172]: Invalid user server from 109.250.150.110 Dec 6 06:00:00 [host] sshd[22172]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.250.150.110 Dec 6 06:00:02 [host] sshd[22172]: Failed password for invalid user server from 109.250.150.110 port 51348 ssh2 |
2019-12-06 13:07:53 |
| 183.150.250.45 | attack | WordPress brute force |
2019-12-06 09:50:49 |
| 71.6.232.9 | attackspambots | From CCTV User Interface Log ...::ffff:71.6.232.9 - - [05/Dec/2019:19:06:52 +0000] "GET / HTTP/1.1" 200 960 ... |
2019-12-06 10:02:57 |
| 165.227.69.39 | attack | SSH invalid-user multiple login attempts |
2019-12-06 10:08:25 |
| 208.91.198.76 | attack | WordPress brute force |
2019-12-06 09:49:30 |
| 103.44.27.58 | attack | Dec 5 20:20:46 ny01 sshd[12284]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.44.27.58 Dec 5 20:20:48 ny01 sshd[12284]: Failed password for invalid user emanuel from 103.44.27.58 port 34325 ssh2 Dec 5 20:27:24 ny01 sshd[13269]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.44.27.58 |
2019-12-06 10:14:10 |
| 77.199.87.64 | attackspambots | Dec 5 14:26:16 web9 sshd\[11132\]: Invalid user smile from 77.199.87.64 Dec 5 14:26:16 web9 sshd\[11132\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.199.87.64 Dec 5 14:26:19 web9 sshd\[11132\]: Failed password for invalid user smile from 77.199.87.64 port 57669 ssh2 Dec 5 14:31:58 web9 sshd\[12073\]: Invalid user password from 77.199.87.64 Dec 5 14:31:58 web9 sshd\[12073\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.199.87.64 |
2019-12-06 09:54:32 |
| 209.105.243.145 | attack | Dec 6 01:40:38 zeus sshd[28781]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.105.243.145 Dec 6 01:40:39 zeus sshd[28781]: Failed password for invalid user sip from 209.105.243.145 port 48854 ssh2 Dec 6 01:46:00 zeus sshd[28928]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.105.243.145 Dec 6 01:46:02 zeus sshd[28928]: Failed password for invalid user questell from 209.105.243.145 port 53654 ssh2 |
2019-12-06 10:10:14 |
| 200.89.178.214 | attack | Dec 5 20:08:19 XXX sshd[8147]: Invalid user guest from 200.89.178.214 port 56362 |
2019-12-06 10:15:06 |
| 219.84.236.108 | attackspam | Dec 5 21:00:03 goofy sshd\[28806\]: Invalid user pi from 219.84.236.108 Dec 5 21:00:03 goofy sshd\[28806\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.84.236.108 Dec 5 21:00:03 goofy sshd\[28807\]: Invalid user pi from 219.84.236.108 Dec 5 21:00:04 goofy sshd\[28807\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.84.236.108 Dec 5 21:00:05 goofy sshd\[28806\]: Failed password for invalid user pi from 219.84.236.108 port 48906 ssh2 |
2019-12-06 09:55:19 |
| 130.162.64.72 | attack | Dec 6 07:35:47 vtv3 sshd[32581]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=130.162.64.72 Dec 6 07:35:50 vtv3 sshd[32581]: Failed password for invalid user toni from 130.162.64.72 port 64323 ssh2 Dec 6 07:41:50 vtv3 sshd[3302]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=130.162.64.72 Dec 6 07:54:12 vtv3 sshd[9486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=130.162.64.72 Dec 6 07:54:14 vtv3 sshd[9486]: Failed password for invalid user karlsdottir from 130.162.64.72 port 51518 ssh2 Dec 6 08:00:32 vtv3 sshd[12824]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=130.162.64.72 |
2019-12-06 13:03:17 |
| 111.11.103.198 | attack | Dec 5 20:15:24 XXX sshd[22364]: Invalid user ubnt from 111.11.103.198 port 49581 |
2019-12-06 10:03:59 |