123.108.68.0/24
At a glance
Addresses
/24 block
Visibility
74 of 76 vantage points
RPKI
Registry
AUAllocated 1st February 2007
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS23871seen on 3,687 paths from 120 vantage points
- Peer of AS7474seen on 84,519 paths from 133 vantage points
- Peer of AS7473seen on 157,979 paths from 109 vantage points
- Peer of AS6461seen on 133,430 paths from 5 vantage points
- Peer of AS25091seen on 665,606 paths from 2 vantage points
SG
US
CHOne 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
- London, UK2387169398529This path
- Oregon, US23871693920130This path
- Singapore2387169393862323673This path
- Sao Paulo2387174743257291435280This path
- Amsterdam23871747474736461250918298Shown 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
97%
Seen by 74 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
- APNIC — Asia-Pacific
- Country
- Australia
- Allocated
- 1st February 2007
- Allocation block
- 123.108.68.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 |
|---|---|---|
| 123.108.68.0/23 | AS23871 | /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 |
|---|---|---|---|
| 123.108.69.0/24 | 256 | AS23871Australia Internet Solutions | 74/76 |
History
- AS2387114th 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 123.108.68.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.