79.127.32.0/20
At a glance
Addresses
/20 block
Visibility
1 of 76 vantage points
RPKI
Registry
IRAllocated 17th September 2007
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 AS43754seen on 164,611 paths from 138 vantage points
- Peer of AS41689seen on 164,611 paths from 138 vantage points
- Peer of AS49666seen on 57,262 paths from 76 vantage points
- Peer of AS33891seen on 25,658 paths from 75 vantage points
- Peer of AS1299seen on 66,133 paths from 30 vantage points
- Peer of AS6762seen on 33,263 paths from 1 vantage point
- Peer of AS1680seen on 35,566 paths from 1 vantage point
DE
SE
IT
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.
Route visibility
1%
Seen by 1 of 76 full-feed vantage points
Seen by few vantage pointsObserved at 1 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
- 17th September 2007
- Allocation block
- 79.127.0.0/17
- Status
- allocated
- Origin validation
- Invalid
A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.
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 |
|---|---|---|---|
| 79.127.32.0/19 | 8.2k | AS43754Asiatech Data Transmission company | 76/76 |
| 79.127.0.0/18 | 16.4k | AS43754Asiatech Data Transmission company | 76/76 |
| 79.127.0.0/17 | 32.8k | AS43754Asiatech Data Transmission company | 76/76 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 79.127.44.0/23 | 512 | AS44400Ertebatat Sabet Parsian Co. PJS | 76/76 |
| 79.127.42.0/24 | 256 | AS43754Asiatech Data Transmission company | 76/76 |
| 79.127.46.0/24 | 256 | AS43415Secure Infrastructure of Transactional Services Company PJSC | 76/76 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 79.127.48.0/20 | 4.1k | AS43754Asiatech Data Transmission company | 76/76 |
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 79.127.32.0/20 in the calculator/20 reference
Routing data derived from RouteViews MRT archives and public registry data.