206.62.69.0/24
At a glance
Addresses
/24 block
Visibility
78 of 80 vantage points
RPKI
Registry
USAllocated 25th July 1995
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS61625seen on 78 paths from 78 vantage points
- Peer of AS266152seen on 816 paths from 134 vantage points
- Peer of AS262773seen on 13,013 paths from 142 vantage points
- Peer of AS61568seen on 9,209 paths from 68 vantage points
- Peer of AS1031seen on 5,328 paths from 2 vantage points
BR
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
- Sao Paulo61625266152266213This path
- London, UK616252661521374098529This path
- Amsterdam6162526615226761334549213151This path
- Singapore61625266152262773615681031132337Shown above
- Oregon, US61625266152618321378632572335220130This 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 78 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
- ARIN — North America
- Country
- United States
- Allocated
- 25th July 1995
- Allocation block
- 206.62.0.0/16
- 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 |
|---|---|---|
| 206.62.68.0/22 | AS61625 | /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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 206.62.68.0/22 | 1k | AS61625Grupo We Dev LTDA | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 206.62.68.0/24 | 256 | AS61625Grupo We Dev LTDA | 79/80 |
History
- AS6162512th 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 206.62.69.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.