213.176.22.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
IRAllocated 8th October 1999
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS59441seen on 836 paths from 76 vantage points
- Peer of AS48011seen on 1,237 paths from 108 vantage points
- Peer of AS49127seen on 6,104 paths from 112 vantage points
- Peer of AS137409seen on 5,388 paths from 1 vantage point
- Peer of AS8551seen on 1,077,043 paths from 1 vantage point
TR
NL
AU
IL
PSOne 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
- Amsterdam5944148011491271374098298This path
- London, UK5944148011491271374098529This path
- Sao Paulo59441480114912713740935280This path
- Singapore59441480114912713740923673This path
- Oregon, US594414801149127137409855142013Shown above
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 76 of 76 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
- 8th October 1999
- Allocation block
- 213.176.0.0/19
- 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 |
|---|---|---|---|
| 213.176.20.0/22 | 1k | AS44947AMWAJ ALKHYR COMMERCIAL BROKERS CO. | 1/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 213.176.23.0/24 | 256 | AS59441NOAVARAN SHABAKEH SABZ MEHREGAN (Ltd.) | 76/76 |
History
- AS5944131st 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 213.176.22.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.