Log in to view charts and search reports for this IP.
Log In
No reports in the last 60 days
20.213.139.102 has been reported 8
times. The most recent report is from
.
The full history is preserved below and remains searchable. A
0% score reflects the absence of recent activity, but
this is not a guarantee that earlier reports were invalid. Abuse confidence score decays,
naturally, over time, when the abusive activity stops.
IP Abuse Reports for 20.213.139.102:
This IP address has been reported a total of
8
times from
5 distinct
sources.
20.213.139.102 was first reported on
, and the most recent report was
.
[Jun 6 13:29:04] NOTICE[190880] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '<sip:8011@4 ...
show more[Jun 6 13:29:04] NOTICE[190880] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '<sip:[email protected]>' failed for '20.213.139.102:49249' (callid: d5e8498454037b9ec04897469745f01f) - No matching endpoint found
show less
[Jun 6 04:44:51] NOTICE[185770] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '<sip:2001@4 ...
show more[Jun 6 04:44:51] NOTICE[185770] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '<sip:[email protected]>' failed for '20.213.139.102:57574' (callid: 5f2cc7b4b00dff65155a1a8cb3733abf) - No matching endpoint found
show less
[Jun 6 03:35:39] NOTICE[185114] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '<sip:101@45 ...
show more[Jun 6 03:35:39] NOTICE[185114] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '<sip:[email protected]>' failed for '20.213.139.102:54531' (callid: a4f0c6f7b0c56dc7638a7d2330454077) - No matching endpoint found
show less
2022-06-06 03:34:32,433 fail2ban.actions [1100]: NOTICE [asterisk-challenge] Ban 20.213.139. ...
show more2022-06-06 03:34:32,433 fail2ban.actions [1100]: NOTICE [asterisk-challenge] Ban 20.213.139.102
...
show less