Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Mumbai

Region: Maharashtra

Country: India

Internet Service Provider: Reliance

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '115.240.0.0 - 115.247.255.255'

% Abuse contact for '115.240.0.0 - 115.247.255.255' is 'ip.abuse@ril.com'

inetnum:        115.240.0.0 - 115.247.255.255
netname:        RELIANCEJIO-IN
descr:          Reliance Jio Infocomm Limited
country:        IN
org:            ORG-RJIL1-AP
admin-c:        RJIL1-AP
tech-c:         RJIL1-AP
abuse-c:        AR1022-AP
status:         ALLOCATED PORTABLE
remarks:        --------------------------------------------------------
remarks:        To report network abuse, please contact mnt-irt
remarks:        For troubleshooting, please contact tech-c and admin-c
remarks:        Report invalid contact via www.apnic.net/invalidcontact
remarks:        --------------------------------------------------------
mnt-by:         APNIC-HM
mnt-lower:      MAINT-IN-RELIANCEJIO
mnt-routes:     MAINT-IN-RELIANCEJIO
mnt-irt:        IRT-RELIANCEJIO-IN
last-modified:  2020-08-19T13:07:29Z
source:         APNIC

irt:            IRT-RELIANCEJIO-IN
address:        Reliance JIO INFOCOMM LTD GHANSOLI INDIA
e-mail:         ip.abuse@ril.com
abuse-mailbox:  ip.abuse@ril.com
admin-c:        IBSP1-AP
tech-c:         IBSP1-AP
auth:           # Filtered
remarks:        ip.abuse@ril.com was validated on 2026-02-18
mnt-by:         MAINT-IN-RELIANCEJIO
last-modified:  2026-02-18T13:42:51Z
source:         APNIC

organisation:   ORG-RJIL1-AP
org-name:       Reliance Jio Infocomm Limited
org-type:       LIR
country:        IN
address:        Reliance Coporate IT park LTD
address:        Ghansoli NaviMumbai
phone:          +912279670000
fax-no:         +912279610099
e-mail:         ip.management@ril.com
mnt-ref:        APNIC-HM
mnt-by:         APNIC-HM
last-modified:  2023-09-05T02:15:41Z
source:         APNIC

role:           ABUSE RELIANCEJIOIN
country:        ZZ
address:        Reliance JIO INFOCOMM LTD GHANSOLI INDIA
phone:          +000000000
e-mail:         ip.abuse@ril.com
admin-c:        IBSP1-AP
tech-c:         IBSP1-AP
nic-hdl:        AR1022-AP
remarks:        Generated from irt object IRT-RELIANCEJIO-IN
remarks:        ip.abuse@ril.com was validated on 2026-02-18
abuse-mailbox:  ip.abuse@ril.com
mnt-by:         APNIC-ABUSE
last-modified:  2026-02-18T13:43:21Z
source:         APNIC

role:           Reliance Jio Infocomm Limited
address:        Reliance JIO INFOCOMM LTD GHANSOLI INDIA
country:        IN
phone:          +91-44770000
e-mail:         ip.management@ril.com
admin-c:        RJIL1-AP
tech-c:         RJIL1-AP
nic-hdl:        RJIL1-AP
mnt-by:         MAINT-IN-RELIANCEJIO
last-modified:  2016-03-09T23:55:07Z
source:         APNIC

% Information related to '115.246.143.0/24AS55836'

route:          115.246.143.0/24
origin:         AS55836
descr:          Reliance Jio Infocomm Limited
                Reliance Coporate IT park LTD
                Ghansoli NaviMumbai
mnt-by:         MAINT-IN-RELIANCEJIO
last-modified:  2025-01-24T10:23:23Z
source:         APNIC

% This query was served by the APNIC Whois Service version 1.88.36-SNAPSHOT (WHOIS-AU5)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 115.246.143.17
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2116
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;115.246.143.17.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026032401 1800 900 604800 86400

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 25 05:59:28 CST 2026
;; MSG SIZE  rcvd: 107
Host info
Host 17.143.246.115.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 17.143.246.115.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
99.46.143.22 attackbots
Aug  2 17:06:53 vps200512 sshd\[22059\]: Invalid user recovery from 99.46.143.22
Aug  2 17:06:53 vps200512 sshd\[22059\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=99.46.143.22
Aug  2 17:06:54 vps200512 sshd\[22059\]: Failed password for invalid user recovery from 99.46.143.22 port 48652 ssh2
Aug  2 17:11:09 vps200512 sshd\[22188\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=99.46.143.22  user=root
Aug  2 17:11:11 vps200512 sshd\[22188\]: Failed password for root from 99.46.143.22 port 41352 ssh2
2019-08-03 05:27:31
162.247.74.204 attackbots
Aug  2 22:28:29 vpn01 sshd\[26042\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.247.74.204  user=root
Aug  2 22:28:31 vpn01 sshd\[26042\]: Failed password for root from 162.247.74.204 port 59126 ssh2
Aug  2 22:28:35 vpn01 sshd\[26058\]: Invalid user cirros from 162.247.74.204
2019-08-03 04:48:10
117.50.49.74 attackbotsspam
2019-08-02T20:32:02.579278abusebot-7.cloudsearch.cf sshd\[12494\]: Invalid user king from 117.50.49.74 port 36027
2019-08-03 04:44:51
134.209.100.31 attackbots
Aug  3 02:29:41 itv-usvr-02 sshd[6862]: Invalid user administrator from 134.209.100.31 port 46996
Aug  3 02:29:41 itv-usvr-02 sshd[6862]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.100.31
Aug  3 02:29:41 itv-usvr-02 sshd[6862]: Invalid user administrator from 134.209.100.31 port 46996
Aug  3 02:29:43 itv-usvr-02 sshd[6862]: Failed password for invalid user administrator from 134.209.100.31 port 46996 ssh2
Aug  3 02:29:43 itv-usvr-02 sshd[6865]: Invalid user administrator from 134.209.100.31 port 47826
2019-08-03 04:44:12
185.220.101.30 attackbots
(sshd) Failed SSH login from 185.220.101.30 (-): 5 in the last 3600 secs
2019-08-03 05:11:16
198.211.102.9 attackbotsspam
Aug  2 16:53:45 TORMINT sshd\[18440\]: Invalid user omega from 198.211.102.9
Aug  2 16:53:45 TORMINT sshd\[18440\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.211.102.9
Aug  2 16:53:47 TORMINT sshd\[18440\]: Failed password for invalid user omega from 198.211.102.9 port 57172 ssh2
...
2019-08-03 05:15:46
165.227.92.185 attackspam
Aug  2 22:16:34 ArkNodeAT sshd\[22972\]: Invalid user tuan from 165.227.92.185
Aug  2 22:16:34 ArkNodeAT sshd\[22972\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.92.185
Aug  2 22:16:36 ArkNodeAT sshd\[22972\]: Failed password for invalid user tuan from 165.227.92.185 port 58508 ssh2
2019-08-03 05:28:33
218.92.0.154 attack
Aug  2 21:29:48 legacy sshd[30892]: Failed password for root from 218.92.0.154 port 38378 ssh2
Aug  2 21:30:01 legacy sshd[30892]: error: maximum authentication attempts exceeded for root from 218.92.0.154 port 38378 ssh2 [preauth]
Aug  2 21:30:07 legacy sshd[30900]: Failed password for root from 218.92.0.154 port 44129 ssh2
...
2019-08-03 04:47:14
189.84.19.51 attack
19/8/2@15:30:15: FAIL: Alarm-Intrusion address from=189.84.19.51
...
2019-08-03 04:47:51
41.94.97.138 attackbots
Aug  2 21:55:46 mail sshd\[31316\]: Failed password for root from 41.94.97.138 port 60468 ssh2
Aug  2 22:13:25 mail sshd\[31565\]: Invalid user solr from 41.94.97.138 port 48608
Aug  2 22:13:25 mail sshd\[31565\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.94.97.138
...
2019-08-03 05:22:07
92.118.160.13 attackspam
02.08.2019 19:32:09 IMAP access blocked by firewall
2019-08-03 05:05:15
201.6.122.167 attackbotsspam
Aug  2 22:21:43 localhost sshd\[60141\]: Invalid user alex from 201.6.122.167 port 60993
Aug  2 22:21:43 localhost sshd\[60141\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.6.122.167
...
2019-08-03 05:22:41
171.244.140.174 attackbots
Aug  2 22:42:43 eventyay sshd[32571]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.244.140.174
Aug  2 22:42:45 eventyay sshd[32571]: Failed password for invalid user ea from 171.244.140.174 port 23727 ssh2
Aug  2 22:48:02 eventyay sshd[1377]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.244.140.174
...
2019-08-03 04:56:41
45.160.26.48 attackspambots
2019-08-02T19:57:46.281440abusebot-7.cloudsearch.cf sshd\[12387\]: Invalid user linda from 45.160.26.48 port 14813
2019-08-03 04:46:27
181.115.147.123 attackbotsspam
Automatic report - Port Scan Attack
2019-08-03 04:56:08

Recently Reported IPs

93.81.136.178 110.78.154.199 2606:4700:10::6814:7984 2606:4700:10::6814:7778
180.153.236.243 180.153.236.179 14.212.68.19 77.237.240.191
2606:4700:10::6816:62 2606:4700:10::6814:4467 2606:4700:10::ac43:2830 2606:4700:10::ac43:105e
2606:4700:10::6814:7056 2606:4700:10::6816:2369 2606:4700:10::6814:7678 2606:4700:10::6814:4849
2606:4700:10::6814:7450 2606:4700:10::6816:3204 2606:4700:10::6814:7211 2606:4700:10::6816:4845