SUBNET.IM

94.156.226.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCBG

Allocated 27th August 2008

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 94.156.226.0/24 as seen from Singapore, read outward from the origin: AS57463 → AS6939 → AS132337. Each hop is listed with its network name beneath the graph.AS57463NetIX Communicati…OriginAS6939Hurricane Electri…AS132337Axclusive

Seen from Singapore

  1. Peer of AS57463seen on 7,440 paths from 49 vantage points
  2. Peer of AS6939seen on 320,794 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage point

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. Singapore574636939132337Shown above
  2. Oregon, US57463693920130This path
  3. London, UK5746351601410958529This path
  4. Sao Paulo5746351601410953356266213This path
  5. Amsterdam5746351601505096762291434549213151This 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

99%

Seen by 79 of 80 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
Bulgaria
Allocated
27th August 2008
Allocation block
94.156.226.0/24
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 94.156.226.0/24
ROA prefixAuthorised originMax length
94.156.226.0/24AS57463/32

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 94.156.226.0/24
PrefixAddressesOriginVisibility
94.156.227.0/24256AS50837CLOUDSIGMA AG80/80

History

  1. AS5746312th August 2026 present
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 94.156.226.0/24 in the calculator/24 reference

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