IP abuse report138.128.246.146

Critical Residential IPv4 United States AS396948

138.128.246.146 is an IPv4 address located in Santa Clara, United States. It belongs to a network operated by Kamatera, Inc. (AS396948). The address is listed by 5 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 5 Community Reports 0 How the score works
Provider notified This IP was reported to its network operator Kamatera, Inc. · 2026-11-08 · IPDB-AR-006934 Acknowledged Show detailsHide
  1. DetectedScore 90/100
  2. Notice sent2026-11-08 06:33
  3. Deliveredcloudwm.com
  4. Operator response Acknowledged

The IP-DB Abuse Desk sent an abuse notice with supporting evidence to Kamatera, Inc.'s registered abuse contact on 2026-11-08 06:33: abuse@cloudwm.com

Acknowledged / ticket opened 2026-11-08 06:33 · Ticket 36483417
IP-DB Abuse Desk, We examine all abuse reports with up to 48 hours. If this ticket requires immediate attention, please reach out by a phone call to our 24/7 Technical Support representatives in order for it to be handled instantly. Note: Please make sure tha…
This notice covers 1 address(es) on the same network. View public record · IPDB-AR-006934 →
Listing sources5
Community Reports0
Distinct Reporters0
Last seen 15 minutes ago

IP Information

ISP / Organization
Kamatera, Inc.
ASN
AS396948 CLOUDWEBMANAGE-SC
ASN Domain
cloudwm.com
IP Range
138.128.246.0/24
Regional Registry
ARIN
Connection Type
Residential
Country
United States (US)
Region / State
California
City
Santa Clara
Time Zone
Unknown
Abuse contact
abuse@cloudwm.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
Santa Clara California, United States
Coordinates
37.40, -121.96
Network
AS396948 Kamatera, Inc.
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

138.128.246.0/24

No other address in 138.128.246.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

5

In our pool since: 2026-11-04 06:22 (15 days ago) · Last confirmed: 2026-11-20 03:49

Attack Source 2
SourceScopeFirst seenConfirmed
Blocklist.de (all) Single address 2026-11-19 21:56 2026-11-20 03:4717 minutes ago
Data-Shield IPv4 Blocklist Single address 2026-11-07 19:33 2026-11-20 03:4915 minutes ago
Malicious Activity 2
SourceScopeFirst seenConfirmed
ThreatView High Confidence Single address 2026-11-20 02:47 2026-11-20 03:4817 minutes ago
Malicious IP (romainmarcoux) Aggregator Single address 2026-11-08 09:18 2026-11-20 03:4916 minutes ago
SSH Brute Force 1
SourceScopeFirst seenConfirmed
Blocklist.de SSH Single address 2026-11-19 21:56 2026-11-20 03:4717 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 138.128.246.146 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 138.128.246.146 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 138.128.246.146 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 138.128.246.146 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
15 days ago
2026-11-04 06:22

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 138.128.246.146

Is 138.128.246.146 safe?

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

Who owns 138.128.246.146?

138.128.246.146 is announced by AS396948 and operated by Kamatera, Inc.. It sits in the 138.128.246.0/24 block registered with ARIN.

Where is 138.128.246.146 located?

Geolocation places 138.128.246.146 in Santa Clara, United States. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 138.128.246.146 on a blacklist?

Yes. 138.128.246.146 is currently listed by 5 threat sources: Blocklist.de (all), Blocklist.de SSH, ThreatView High Confidence, Malicious IP (romainmarcoux), Data-Shield IPv4 Blocklist.

How do I report abuse from 138.128.246.146?

Send your log lines to the network's abuse contact, abuse@cloudwm.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/138.128.246.146

Guides for this IP