78.109.233.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
IQAllocated 25th July 2007
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 AS198169seen on 70 paths from 70 vantage points
- Peer of AS211970seen on 1,200 paths from 142 vantage points
- Peer of AS208293seen on 460 paths from 80 vantage points
- Peer of AS39216seen on 2,948 paths from 142 vantage points
- Peer of AS21277seen on 4,803 paths from 142 vantage points
- Peer of AS1299seen on 403,291 paths from 2 vantage points
SE
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
- Singapore19816942705208293210021132337This path
- London, UK198169211970208293392162127712998529Shown above
- Amsterdam1981692119702082933921621277129934549213151This path
- Sao Paulo1981692119702082933921621277349843356266213This path
- Oregon, US19816921197020829339216212773498433566939→ ⋯This 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Iraq
- Allocated
- 25th July 2007
- Allocation block
- 78.109.224.0/20
- 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.
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 |
|---|---|---|---|
| 78.109.232.0/24 | 256 | AS205906Informatics and Telecommunications Public Company (ITPC) | 79/80 |
History
- AS19816912th 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 78.109.233.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.