223.27.227.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
THAllocated 1st September 2010
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS132821seen on 97 paths from 80 vantage points
- Peer of AS38794seen on 16,380 paths from 133 vantage points
- Peer of AS45796seen on 3,401 paths from 64 vantage points
- Peer of AS4637seen on 16,519 paths from 2 vantage points
HK
AEOne 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
- Singapore1328213879445796132337This path
- Amsterdam13282138794457966939213151This path
- London, UK132821387944579646378529Shown above
- Sao Paulo13282138794457966939266213This path
- Oregon, US1328213879445796693920130This 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
- APNIC — Asia-Pacific
- Country
- Thailand
- Allocated
- 1st September 2010
- Allocation block
- 223.27.192.0/18
- 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 |
|---|---|---|---|
| 223.27.224.0/19 | 8.2k | AS38794UIH | 80/80 |
| 223.27.192.0/18 | 16.4k | AS38794UIH | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 223.27.226.0/24 | 256 | AS38794UIH | 80/80 |
History
- AS13282112th 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 223.27.227.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.