194.1.134.0/24
At a glance
Addresses
/24 block
Visibility
79 of 81 vantage points
RPKI
Registry
KGAllocated 27th November 1995
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 AS50053seen on 866 paths from 145 vantage points
- Peer of AS8285seen on 5,106 paths from 145 vantage points
- Peer of AS9002seen on 219,991 paths from 29 vantage points
- Peer of AS6453seen on 666,978 paths from 6 vantage points
LV
GB
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
- Singapore500538285174132337This path
- Amsterdam5005382859002250918298This path
- London, UK500538285174129935280This path
- Sao Paulo5005382859002645335280Shown above
- Oregon, US5005382859002693920130This 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 79 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
- Kyrgyzstan
- Allocated
- 27th November 1995
- Allocation block
- 194.1.132.0/22
- Status
- assigned
- 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 |
|---|---|---|
| 194.1.134.0/24 | AS50053 | /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 |
|---|---|---|---|
| 194.1.135.0/24 | 256 | AS50053Anton Levin | 81/81 |
History
- AS5005322nd September 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 194.1.134.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.