Data as of Nov 21, 2026

128.0.144.0/23

1 residential-proxy exit · 30 days

mywire Datentechnik GmbH

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
0.20% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
4
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

2 observations

Proxy providers listing exits

  • Byteful
  • FLAMEPROXIES_BASIC
  • GEEKPROXY_TURBO
  • PROXYSCRAPE

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
128.0.144.0 - 128.0.155.2553,072DE-MYWIRE-20120914mywire Datentechnik GmbH (ORG-MDG9-RIPE) · DEALLOCATED PASep 28, 2012abuse@my-wire.de
└ 128.0.144.128/2816MYWIRENET-CUST01-CPEmywire Datentechnik GmbHASSIGNED PAFeb 5, 2013abuse@my-wire.de
via DE-MYWIRE-20120914
└ 128.0.144.152/298MYWIRENET-CUST01-CPEmywire Datentechnik GmbHASSIGNED PAAug 20, 2013abuse@my-wire.de
via DE-MYWIRE-20120914
└ 128.0.145.0/24256MYWIRENET-CUST01-CPEmywire Datentechnik GmbHASSIGNED PAMay 17, 2016abuse@my-wire.de
via DE-MYWIRE-20120914

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Sep 2014
Current origin since
Sep 2014 · 12 yr
Origin networks
1