5.175.204.0/24
At a glance
Addresses
/24 block
Visibility
77 of 81 vantage points
RPKI
Registry
DEAllocated 2nd August 2012
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 AS219529seen on 596 paths from 111 vantage points
- Peer of AS52025seen on 242 paths from 22 vantage points
- Peer of AS48070seen on 53 paths from 11 vantage points
- Peer of AS6939seen on 988,025 paths from 1 vantage point
RU
GB
USOne 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
- Amsterdam2195298298This path
- London, UK2195295202535280This path
- Sao Paulo21952920594121046413740935280This path
- Singapore21952920594121645650263132337This path
- Oregon, US2195295202548070693920130Shown 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
95%
Seen by 77 of 81 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
- Germany
- Allocated
- 2nd August 2012
- Allocation block
- 5.175.128.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.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 5.175.204.0/24 | AS12586 | /24 |
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 5.175.205.0/24 | 256 | AS12586GHOSTnet GmbH | 80/81 |
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 5.175.204.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.