5.202.3.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
IRAllocated 29th August 2012
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS34918seen on 7,029 paths from 80 vantage points
- Peer of AS49100seen on 31,517 paths from 80 vantage points
- Peer of AS43754seen on 152,403 paths from 142 vantage points
- Peer of AS41689seen on 152,403 paths from 142 vantage points
- Peer of AS49666seen on 285,689 paths from 80 vantage points
- Peer of AS29049seen on 15,071 paths from 109 vantage points
- Peer of AS6663seen on 2,508 paths from 2 vantage points
AZ
RO
DEOne 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
- Oregon, US3491849100437544168949666693920130This path
- Amsterdam3491849100437544168949666290496663213151Shown above
- London, UK34918491004375441689496662904912998529This path
- Sao Paulo349184910043754416894966629049207643356→ ⋯This path
- Singapore3491849100437544168949666290496663132337This 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 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
- 29th August 2012
- Allocation block
- 5.202.0.0/16
- 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.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 5.202.0.0/20 | 4.1k | AS34918Pishgaman Toseeh Ertebatat Company (Private Joint Stock) | 79/80 |
| 5.202.0.0/17 | 32.8k | AS49100Pishgaman Toseeh Ertebatat Company (Private Joint Stock) | 80/80 |
| 5.202.0.0/16 | 65.5k | AS49100Pishgaman Toseeh Ertebatat Company (Private Joint Stock) | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 5.202.2.0/24 | 256 | AS34918Pishgaman Toseeh Ertebatat Company (Private Joint Stock) | 80/80 |
History
- AS3491812th 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 5.202.3.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.