23.195.74.0/24
Vodafone Idea (Vodafone India)AS38266
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
1 of 77 vantage points
RPKI
Registry
USAllocated 12th July 2013
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 AS38266seen on 139,891 paths from 140 vantage points
- Peer of AS55410seen on 60,787 paths from 133 vantage points
- Peer of AS9498seen on 1,909 paths from 32 vantage points
- Peer of AS6762seen on 32,903 paths from 1 vantage point
- Peer of AS1680seen on 35,240 paths from 1 vantage point
IN
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 77 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
- ARIN — North America
- Country
- United States
- Allocated
- 12th July 2013
- Allocation block
- 23.192.0.0/11
- 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.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 23.192.0.0/11 | AS20940 | /11 |
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 |
|---|---|---|---|
| 23.192.0.0/11 | 2.1M | AS20940Akamai International B.V. | 76/77 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 23.195.75.0/24 | 256 | AS35994Akamai Technologies, Inc. | 77/77 |
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 23.195.74.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.