subnet.im

46.232.237.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCUA

Allocated 18th February 2011

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to London, UK.

OriginVantage point · London, UK
One AS path to 46.232.237.0/24 as seen from London, UK, read outward from the origin: AS218538 → AS216211 → AS6939 → AS8529. Each hop is listed with its network name beneath the graph.AS218538ARGSMENT LIMITEDOriginAS216211CYBERVERSE LLCAS6939Hurricane Electri…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS218538seen on 112 paths from 112 vantage points
  2. Peer of AS216211seen on 4,837 paths from 55 vantage points
  3. Peer of AS6939seen on 234,748 paths from 8 vantage points

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. London, UK21853821621169398529Shown above
  2. Sao Paulo21853840792291435280This path
  3. Singapore218538216211335623673This path
  4. Amsterdam2185382162113356250918298This path
  5. Oregon, US21853821621133561299855142013This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

100%

Seen by 76 of 76 full-feed vantage points

Globally propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
RIPE NCC — Europe, Middle East, Central Asia
Country
Ukraine
Allocated
18th February 2011
Allocation block
46.232.232.0/21
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 46.232.237.0/24
ROA prefixAuthorised originMax length
46.232.237.0/24AS218538/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 46.232.237.0/24
PrefixAddressesOriginVisibility
46.232.236.0/24256AS219521VERSADC VERI MERKEZI HIZMETLERI LIMITED SIRKETI76/76

History

  1. AS2185384th October 2026 — present
  2. AS20351612th August 2026 — 25th September 2026
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 46.232.237.0/24 in the calculator/24 reference

Routing data derived from RouteViews MRT archives and public registry data.