168.222.48.0/24
HGC Global Communications LimitedAS9304
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
21 of 78 vantage points
RPKI
Registry
USAllocated 12th August 1994
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 AS205489seen on 659 paths from 78 vantage points
- Peer of AS215120seen on 463 paths from 140 vantage points
- Peer of AS49581seen on 44,960 paths from 128 vantage points
- Peer of AS44592seen on 9,620 paths from 67 vantage points
- Peer of AS64289seen on 389 paths from 4 vantage points
- Peer of AS46427seen on 51 paths from 1 vantage point
- Peer of AS6762seen on 33,218 paths from 1 vantage point
- Peer of AS1680seen on 35,557 paths from 1 vantage point
GB
AT
DE
NL
IT
IL
PSOne 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
- Singapore930415412693923673This path
- Oregon, US2054892151204958144592642894642767621680→ ⋯Shown 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
27%
Seen by 21 of 78 full-feed vantage points
Seen by few vantage pointsObserved at 1 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
- United States
- Allocated
- 12th August 1994
- Allocation block
- 168.222.0.0/17
- Status
- assigned
- Origin validation
- Invalid
A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 168.222.48.0/24 | AS834 | /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 |
|---|---|---|---|
| 168.222.49.0/24 | 256 | AS16276OVH SAS | 78/78 |
History
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 168.222.48.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.