109.111.44.0/22
At a glance
Addresses
/22 block
Visibility
78 of 78 vantage points
RPKI
Registry
AUAllocated 24th November 2009
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 AS272547seen on 2,403 paths from 141 vantage points
- Peer of AS270353seen on 873 paths from 121 vantage points
- Peer of AS23106seen on 15,807 paths from 107 vantage points
- Peer of AS7195seen on 12,848 paths from 1 vantage point
- Peer of AS8551seen on 1,077,280 paths from 1 vantage point
BR
CO
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
- Sao Paulo27254727035335280This path
- London, UK27254727035369398529This path
- Amsterdam2725472703532310671958298This path
- Singapore27254727035323106719523673This path
- Oregon, US272547270353231067195855142013Shown 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
100%
Seen by 78 of 78 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
- Australia
- Allocated
- 24th November 2009
- Allocation block
- 109.111.32.0/19
- 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 |
|---|---|---|
| 109.111.44.0/22 | AS272547 | /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
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 109.111.44.0/23 | 512 | AS272547Servicos de Infraestrutura e Datacenter | 78/78 |
| 109.111.46.0/23 | 512 | AS272547Servicos de Infraestrutura e Datacenter | 78/78 |
| 109.111.44.0/24 | 256 | AS272547Servicos de Infraestrutura e Datacenter | 78/78 |
| 109.111.45.0/24 | 256 | AS272547Servicos de Infraestrutura e Datacenter | 78/78 |
| 109.111.46.0/24 | 256 | AS272547Servicos de Infraestrutura e Datacenter | 78/78 |
| 109.111.47.0/24 | 256 | AS272547Servicos de Infraestrutura e Datacenter | 78/78 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
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 109.111.44.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.