170.83.76.0/22
At a glance
Addresses
/22 block
Visibility
80 of 80 vantage points
RPKI
Registry
VEAllocated 3rd January 2017
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS266841seen on 301 paths from 142 vantage points
- Peer of AS264628seen on 2,020 paths from 142 vantage points
- Peer of AS270042seen on 1,660 paths from 142 vantage points
- Peer of AS7195seen on 9,346 paths from 2 vantage points
CO
SGOne 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
- Amsterdam2668412646282700427195213151This path
- London, UK26684126462827004271958529This path
- Sao Paulo2668412646282700427195266213This path
- Singapore2668412646282700427195132337Shown above
- Oregon, US2668412646282700427195693920130This 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
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
- LACNIC — Latin America and the Caribbean
- Country
- Venezuela
- Allocated
- 3rd January 2017
- Allocation block
- 170.83.76.0/22
- Status
- allocated
- 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 |
|---|---|---|
| 170.83.76.0/22 | AS266841 | /24 |
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
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 170.83.76.0/24 | 256 | AS266841GALANET SOLUTION C.A. | 79/80 |
| 170.83.77.0/24 | 256 | AS266841GALANET SOLUTION C.A. | 79/80 |
| 170.83.78.0/24 | 256 | AS266841GALANET SOLUTION C.A. | 79/80 |
| 170.83.79.0/24 | 256 | AS266841GALANET SOLUTION C.A. | 79/80 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 170.83.72.0/22 | 1k | AS262907Brasil TecPar | 80/80 |
History
- AS26684112th 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 170.83.76.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.