204.93.192.0/19
At a glance
Addresses
/19 block
Visibility
78 of 80 vantage points
RPKI
Registry
USAllocated 12th June 2009
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS23352seen on 15,784 paths from 118 vantage points
- Peer of AS6461seen on 101,772 paths from 33 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
BROne 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, US2335220130This path
- London, UK2335264618529This path
- Amsterdam23352646134549213151This path
- Sao Paulo2335264613356266213Shown above
- Singapore2335264618966132337This 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
98%
Seen by 78 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
- ARIN — North America
- Country
- United States
- Allocated
- 12th June 2009
- Allocation block
- 204.93.128.0/17
- Status
- allocated
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
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 |
|---|---|---|---|
| 204.93.128.0/17 | 32.8k | AS23352DEFT.COM | 78/80 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 204.93.193.0/24 | 256 | AS23352DEFT.COM | 78/80 |
| 204.93.195.0/24 | 256 | AS212238Datacamp Limited | 80/80 |
| 204.93.201.0/24 | 256 | AS16509Amazon.com, Inc. | 80/80 |
| 204.93.203.0/24 | 256 | AS23352DEFT.COM | 78/80 |
| 204.93.209.0/24 | 256 | AS212238Datacamp Limited | 80/80 |
| 204.93.217.0/24 | 256 | AS29802HIVELOCITY, Inc. | 80/80 |
| 204.93.221.0/24 | 256 | AS56468MC NETWORKING Sh.p.k. | 78/80 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS2335212th 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 204.93.192.0/19 in the calculator/19 reference
Routing data derived from RouteViews MRT archives and public registry data.