Data as of Nov 12, 2026

46.248.96.0/22

Anonymizer · ISP proxy

British Telecommunications Limited · space held by Burstfire Networks Ltd

Announcement
this exact prefix
RPKI valid
Announced by
Type
ISP proxy
Risk
90 / 100 · Critical
IPv4 market

Path

1 · Holder
record created Dec 20, 2010
2 · Leased from
its owner, directly
3 · Announced by
AS2856 British Telecommunications Limited
since Apr 2026 · 7 mo ago
4 · Use
ISP proxy
anonymizer space, operator not named

Operators, sellers and brokers

Leased from

Owners leasing their own space

NameIn 46.248.96.0/22/24s
Burstfire Networks Ltd
1,024100%
4

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

46.248.96.0/22

From the registry to its use

  1. Dec 20, 2010
    Registry record
    Burstfire Networks Ltd
    ALLOCATED PA
    46.248.96.0/19
  2. Dec 22, 2010– Dec 17, 2022
    Announced
    AS9153 Burstfire Networks Ltd
    as part of 46.248.96.0/19
    46.248.96.0/19
  3. Jan 11, 2023
    Route object
    AS2856 British Telecommunications Limited
    RIPE route object for AS2856 British Telecommunications Limited, maintainer BURSTFIRE-MNT
  4. Jan 11, 2023– Jan 30, 2026
    Announced
    AS2856 British Telecommunications Limited
    Internet provider
  5. Nov 1, 2024– today
    Announced
    AS9153 Burstfire Networks Ltd
    as part of 46.248.96.0/19
    46.248.96.0/19
  6. Apr 25, 2026– today
    Announced
    AS2856 British Telecommunications Limited
    Internet provider

Announcements

Less specific

Covering announcements

PrefixOriginTypeHolderRPKI
46.248.96.0/19
since Nov 2024
AS9153UnknownBurstfire Networks Ltd

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
46.248.96.0/198,192UK-BURSTFIRE-20101220Burstfire Networks Ltd (ORG-BNL1-RIPE) · GBALLOCATED PADec 20, 2010abuse@burstfire.net
└ 46.248.96.0/221,024BTNET-LHLunknownASSIGNED PADec 7, 2022abuse@burstfire.net
via UK-BURSTFIRE-20101220

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
Jan 2023
Current origin since
Apr 2026 · 7 mo
Origin networks
1