Data as of Nov 18, 2026

156.67.248.0/21

2 residential-proxy exits · 30 days

Cityfibre Limited

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

Residential-proxy exits

Proxy exits
2
0.10% of its addresses · 30 days
Spread
2 of 8
/24s with at least one exit
Providers
5
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

28 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
156.67.248.0/2401
156.67.250.0/2401

Proxy providers listing exits

  • AnyIP
  • EnigmaProxy
  • NovaProxy
  • ProxyEmpire
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
156.67.240.0/20
since Mar 2018
AS8468Internet provider13Cityfibre Limited

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
156.67.240.0/204,096CITYFIBRE-L1Cityfibre Limited (ORG-CHL10-RIPE) · GBLEGACYFeb 8, 2016abuse@cityfibre.com
└ 156.67.248.0/24256CITYFIBRE-L1unknownLEGACYSep 5, 2016abuse@cityfibre.com
via CITYFIBRE-L1
└ 156.67.249.0/24256CITYFIBRE-L1SLOUGHLEGACYSep 5, 2016abuse@cityfibre.com
via CITYFIBRE-L1
└ 156.67.250.0/24256CITYFIBRE-L1SOUTHENDLEGACYSep 5, 2016abuse@cityfibre.com
via CITYFIBRE-L1
└ 156.67.251.0/24256CITYFIBRE-L1Milton KeynesLEGACYSep 5, 2016abuse@cityfibre.com
via CITYFIBRE-L1
└ 156.67.252.0/24256CITYFIBRE-L1NOTTINGHAMLEGACYSep 5, 2016abuse@cityfibre.com
via CITYFIBRE-L1
└ 156.67.253.0/24256CITYFIBRE-L1LEICESTERLEGACYSep 5, 2016abuse@cityfibre.com
via CITYFIBRE-L1
└ 156.67.254.0/24256CITYFIBRE-L1DERBYLEGACYSep 5, 2016abuse@cityfibre.com
via CITYFIBRE-L1
└ 156.67.255.0/24256CITYFIBRE-L1CF Core Network (Reserved)LEGACYFeb 15, 2016abuse@cityfibre.com
via CITYFIBRE-L1

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Oct 2018
Current origin since
Oct 2018 · 8.1 yr
Origin networks
1