185.103.198.0/24
AS48678 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/24 block
Visibility
81 of 81 vantage points
RPKI
Registry
TRAllocated 9th June 2015
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 AS201021seen on 5,111 paths from 81 vantage points
- Peer of AS48678seen on 14,322 paths from 145 vantage points
- Peer of AS9121seen on 17,671 paths from 24 vantage points
- Peer of AS6939seen on 988,025 paths from 1 vantage point
USOne 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, UK201021486789121129935280This path
- Sao Paulo201021486789121291435280This path
- Singapore2010214867891218966132337This path
- Oregon, US201021486789121693920130Shown above
- Amsterdam2010214867891211299250918298This 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 81 of 81 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
- Türkiye
- Allocated
- 9th June 2015
- Allocation block
- 185.103.196.0/22
- 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 |
|---|---|---|---|
| 185.103.199.0/24 | 256 | AS201021Ahmet Onur Guney trading as Onur Bilisim Ve Yazilim Hizmetleri | 81/81 |
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 185.103.198.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.