subnet.im

196.49.124.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

AFRINICSL

Allocated 9th December 2025

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 196.49.124.0/24 as seen from Singapore, read outward from the origin: AS329680 → AS209049 → AS329109 → AS60171 → AS132337. Each hop is listed with its network name beneath the graph.AS329680Michcom-IXOriginAS209049MICHCOM LIMITEDAS329109Zoodlabs(SL) Limi…AS60171AFR-IX TELECOM S.…AS132337Axclusive

Seen from Singapore

  1. Peer of AS329680seen on 80 paths from 80 vantage points
  2. Peer of AS209049seen on 1,388 paths from 142 vantage points
  3. Peer of AS329109seen on 6,394 paths from 142 vantage points
  4. Peer of AS60171seen on 1,345 paths from 2 vantage points
  5. 5AS132337AxclusiveSGVantage 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. London, UK329680209049329109601718529This path
  2. Singapore32968020904932910960171132337Shown above
  3. Amsterdam329680209049329109601716939213151This path
  4. Sao Paulo329680209049329109601716939266213This path
  5. Oregon, US32968020904932910960171693920130This 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 80 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
AFRINIC — Africa
Country
Sierra Leone
Allocated
9th December 2025
Allocation block
196.49.124.0/24
Status
assigned
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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

No prefix of the same length in the same parent block is announced.

History

  1. AS32968012th 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 196.49.124.0/24 in the calculator/24 reference

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