31.184.0.0/20
At a glance
Addresses
/20 block
Visibility
75 of 76 vantage points
RPKI
Registry
DEAllocated 17th February 2011
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 AS198967seen on 1,615 paths from 41 vantage points
- Peer of AS174seen on 638,691 paths from 47 vantage points
- Peer of AS6453seen on 652,531 paths from 6 vantage points
US
FROne 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
- Amsterdam1989678298This path
- London, UK1989678529This path
- Singapore1989673389123673This path
- Oregon, US198967855142013This path
- Sao Paulo198967174645335280Shown 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
99%
Seen by 75 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Germany
- Allocated
- 17th February 2011
- Allocation block
- 31.184.0.0/20
- 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 |
|---|---|---|---|
| 31.184.0.0/18 | 16.4k | AS9145EWE TEL GmbH | 1/76 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 31.184.8.0/22 | 1k | AS198967BITel Gesellschaft fuer Telekommunikation mbH | 75/76 |
| 31.184.6.0/23 | 512 | AS198967BITel Gesellschaft fuer Telekommunikation mbH | 55/76 |
| 31.184.14.0/23 | 512 | AS198967BITel Gesellschaft fuer Telekommunikation mbH | 75/76 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 31.184.16.0/20 | 4.1k | AS9145EWE TEL GmbH | 75/76 |
History
- AS19896716th October 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 31.184.0.0/20 in the calculator/20 reference
Routing data derived from RouteViews MRT archives and public registry data.