94.184.34.0/24
At a glance
Addresses
/24 block
Visibility
80 of 81 vantage points
RPKI
Registry
IRAllocated 11th August 2008
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS216169seen on 240 paths from 81 vantage points
- Peer of AS204203seen on 3,236 paths from 81 vantage points
- Peer of AS41881seen on 19,824 paths from 145 vantage points
- Peer of AS43754seen on 171,358 paths from 145 vantage points
- Peer of AS41689seen on 171,358 paths from 145 vantage points
- Peer of AS49666seen on 37,358 paths from 124 vantage points
- Peer of AS12389seen on 21,643 paths from 1 vantage point
- Peer of AS4766seen on 68,670 paths from 2 vantage points
RU
KR
SGOne 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
- Amsterdam21616920420341881437544168949666290498298This path
- London, UK216169204203418814375441689496662904935280This path
- Sao Paulo21616920420341881437544168949666123896939→ ⋯This path
- Singapore21616920420341881437544168949666123894766→ ⋯Shown above
- Oregon, US21616920420341881437544168949666123896939→ ⋯This 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 80 of 81 full-feed vantage points
Globally propagatedObserved 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
- Iran
- Allocated
- 11th August 2008
- Allocation block
- 94.184.0.0/17
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 94.184.35.0/24 | 256 | AS204203Atrin Information & Communications Technology Company PJS | 81/81 |
History
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.184.34.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.