38.110.109.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
USAllocated 16th April 1991
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS207598seen on 1,514 paths from 139 vantage points
- Peer of AS212330seen on 28,870 paths from 139 vantage points
- Peer of AS208293seen on 15,235 paths from 139 vantage points
- 4AS211513Al Lawn Al Akhdar International Company for Communications and Information Technology Ltd.
IQPeer of AS211513seen on 14,038 paths from 139 vantage points - Peer of AS210021seen on 546 paths from 5 vantage points
- Peer of AS25091seen on 663,280 paths from 2 vantage points
CHOne 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
- London, UK2075982123302082932006128529This path
- Amsterdam207598212330208293211513210021250918298Shown above
- Sao Paulo207598212330208293211513210021129935280This path
- Singapore2075982123302082932115132100211299335623673This path
- Oregon, US2075982123302082932115132100211299855142013This 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 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
- ARIN — North America
- Country
- United States
- Allocated
- 16th April 1991
- Allocation block
- 38.0.0.0/8
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 38.110.108.0/22 | AS207598 | /24 |
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 |
|---|---|---|---|
| 38.0.0.0/8 | 16.8M | AS174Cogent Communications, LLC | 74/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 38.110.108.0/24 | 256 | AS207598Iraqcell Communications Co. Ltd. | 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 38.110.109.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.