213.175.78.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
LVAllocated 6th April 2000
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 AS42663seen on 35 paths from 35 vantage points
- Peer of AS5518seen on 3,078 paths from 142 vantage points
- Peer of AS1299seen on 100,308 paths from 35 vantage points
- Peer of AS3257seen on 59,210 paths from 1 vantage point
- Peer of AS23352seen on 103,654 paths from 1 vantage point
SE
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
- Amsterdam4266312578213151This path
- Singapore4266312578132337This path
- London, UK42663551812998529This path
- Sao Paulo42663125783356266213This path
- Oregon, US426635518129932572335220130Shown 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
100%
Seen by 80 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Latvia
- Allocated
- 6th April 2000
- Allocation block
- 213.175.64.0/19
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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 |
|---|---|---|---|
| 213.175.64.0/18 | 16.4k | AS5518SIA Tet | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 213.175.79.0/24 | 256 | AS24921Latvijas Mobilais Telefons SIA | 80/80 |
History
- AS4266312th 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 213.175.78.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.