IP abuse report190.57.233.133

Critical Residential IPv4 Argentina AS20207

190.57.233.133 is an IPv4 address located in Corrientes, Argentina. It belongs to a network operated by Gigared S.A. (AS20207). The address is listed by 7 of the threat-intelligence sources we track and carries a confidence score of 90/100. No community reports have been filed for it yet.

Last updated Listing sources 7 Community Reports 0 How the score works
Provider notified This IP was reported to its network operator Gigared S.A. · 2026-11-15 · IPDB-AR-007737 Awaiting reply Show detailsHide
  1. DetectedScore 90/100
  2. Notice sent2026-11-15 11:33
  3. Deliveredgmail.com
  4. Operator response Waiting · 5 days ago

The IP-DB Abuse Desk sent an abuse notice with supporting evidence to Gigared S.A.'s registered abuse contact on 2026-11-15 11:33: winet.sas@gmail.com

This notice covers 1 address(es) on the same network. View public record · IPDB-AR-007737 →
Listing sources7
Community Reports0
Distinct Reporters0
Last seen 36 minutes ago

IP Information

ISP / Organization
Gigared S.A.
ASN
AS20207 Gigared S.A.
ASN Domain
gigared.com.ar
IP Range
190.57.233.128/28
Regional Registry
LACNIC
Connection Type
Residential
Country
Argentina (AR)
Region / State
Corrientes
City
Corrientes
Time Zone
Unknown
Abuse contact
winet.sas@gmail.com The abuse mailbox this network lists with its regional registry. Report traffic from this IP here, with logs and timestamps.

City is an estimate. The country is reliable; the city varies by provider.

Approximate location

City level
Corrientes Argentina
Coordinates
-27.47, -58.83
Network
AS20207 Gigared S.A.
Open on the threat map

The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.

Network Neighbourhood

190.57.233.0/24

No other address in 190.57.233.0/24 is listed.

An address is not guiltier for having a few listed neighbours, which is why this stays out of the confidence score entirely while the block is mostly clean. It contributes at most 20 points, and only once a substantial share of the block is listed — that ceiling is deliberate: neighbours alone can raise an address to "low" and no further.

Threat Evidence

Last 30 days: how many feeds listed this address each day, and the community reports filed.

Blocklist feeds

Blacklist Matches

7

In our pool since: 2026-08-29 03:47 (2 months ago) · Last confirmed: 2026-11-21 09:19

Aggregated List (Medium Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 2 Aggregator Single address 2026-11-14 14:47 2026-11-21 09:488 minutes ago
Attack Source 3
SourceScopeFirst seenConfirmed
Blocklist.de (all) Single address 2026-11-20 06:17 2026-11-21 09:479 minutes ago
Data-Shield IPv4 Blocklist Single address 2026-11-07 19:33 2026-11-21 09:497 minutes ago
IP-DB Sensor Network Single address 2026-11-16 06:49 2026-11-21 09:506 minutes ago
Malicious Activity 2
SourceScopeFirst seenConfirmed
ThreatView High Confidence Single address 2026-11-21 02:47 2026-11-21 09:488 minutes ago
Malicious IP (romainmarcoux) Aggregator Single address 2026-11-13 14:18 2026-11-21 09:487 minutes ago
SSH Brute Force 1
SourceScopeFirst seenConfirmed
Blocklist.de SSH Single address 2026-11-20 06:17 2026-11-21 09:479 minutes ago

“Confirmed” is the moment the address was still on that source at its most recent fetch — the feeds are replaced wholesale on every refresh. Per-source “first seen” only began being recorded on 30 August 2026, so for listings older than that this column shows the start of record-keeping. The address-level history is the “in our pool since” value above.

IP-DB Sensor · free honeypot

Catch addresses like this on your own server

Sensor opens realistic decoy services — FortiGate, GlobalProtect, Exchange, NetScaler and more — on your server's unused ports. Every address that touches them is logged with evidence, and your firewall, fail2ban and Shield pull the same list to block it.

  • Realistic decoys for VPN gateways, mail, web panels and databases
  • Names exploit attempts by their CVE signature
  • One-command install; runs unprivileged and never touches your real services

While a Sensor reports, your daily API quota rises to 30,000 lookups.

root@web-01 — ipdb-sensor DEMO
● ipdb-sensor.serviceactive (running)
4hits
4decoys
1blocked
  1. 14:02:07 ssh:22 190.57.233.133 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 190.57.233.133 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 190.57.233.133 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 190.57.233.133 Citrix Bleed scan CVE-2023-4966
  5. 14:02:20 ✓ evidence logged → added to your blocklist
Sample output — if this address probed your server

Community Reports 0

Report This IP

No community reports yet for this IP.

Report This IP

Listing History

1
Added to the pool
2 months ago · score at the time: 90/100 · carried by 5 sources
2026-08-29 03:47

The pool is a live picture: an address listed today leaves it when the sources drop it. This record outlives that removal — “listed on 12 August, delisted on 3 September” is truer than either a permanent accusation or a blank page. Events are kept for 400 days.

Frequently asked questions about 190.57.233.133

Is 190.57.233.133 safe?

No. 190.57.233.133 scores 90/100 with strong, recent evidence of abuse (7 sources). Blocking it at your firewall is advisable.

Who owns 190.57.233.133?

190.57.233.133 is announced by AS20207 and operated by Gigared S.A.. It sits in the 190.57.233.128/28 block registered with LACNIC.

Where is 190.57.233.133 located?

Geolocation places 190.57.233.133 in Corrientes, Argentina. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 190.57.233.133 on a blacklist?

Yes. 190.57.233.133 is currently listed by 7 threat sources: Blocklist.de (all), Blocklist.de SSH, ThreatView High Confidence, FireHOL Level 2, Malicious IP (romainmarcoux), Data-Shield IPv4 Blocklist….

How do I report abuse from 190.57.233.133?

Send your log lines to the network's abuse contact, winet.sas@gmail.com, and file a report on IP-DB so others can see it too.

Run this check via the API

The same score and evidence are available as JSON, free with an API key.

API documentation →
curl -H "Key: YOUR_API_KEY" https://ip-db.com/api/v1/check/190.57.233.133

Guides for this IP