subnet.im

217.170.156.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

77 of 77 vantage points

RPKI

No ROA

Registry

AFRINICML

Allocated 17th August 2004

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 217.170.156.0/24 as seen from Singapore, read outward from the origin: AS30985 → AS8346 → AS6762 → AS3356 → AS23673. Each hop is listed with its network name beneath the graph.AS30985Orange Mali SAOriginAS8346SONATEL-AS Autono…AS6762Telecom Italia Sp…AS3356Lumen (Level 3)AS23673Cogetel Online, C…

Seen from Singapore

  1. Peer of AS30985seen on 5,362 paths from 141 vantage points
  2. Peer of AS8346seen on 3,406 paths from 90 vantage points
  3. Peer of AS6762seen on 187,843 paths from 70 vantage points
  4. Peer of AS3356seen on 424,869 paths from 2 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, UK30985834664538529This path
  2. Sao Paulo309858346645335280This path
  3. Amsterdam3098583466762250918298This path
  4. Singapore3098583466762335623673Shown above
  5. Oregon, US3098583466453693920130This 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 77 of 77 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
Mali
Allocated
17th August 2004
Allocation block
217.170.144.0/20
Status
allocated
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.

CoveringMore specific
Prefix hierarchy for 217.170.156.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.217.170.156.0/22AS30985217.170.156.0/24AS30985This prefix

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 217.170.156.0/24
PrefixAddressesOriginVisibility
217.170.156.0/221kAS30985Orange Mali SA77/77

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. AS3098522nd October 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 217.170.156.0/24 in the calculator/24 reference

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