Observed topology
AS47498 iFog GmbH
Unclassified RIPE Route Server
Transit
Upstream networks
Networks observed carrying traffic for AS47498: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
No upstream observed. Typical for a tier-1 network that buys transit from nobody.
Transit
Downstream networks
Networks for which AS47498 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS400688 | Daniel Marks, Sole Proprietorship | Unclassified | IPv4 IPv6 | 6 |
| AS56762 | Olympic Input/Output, LLC | Unclassified | IPv6 | 4 |
| AS203405 | Lin Kai-Lun | Unclassified | IPv6 | 4 |
| AS215743 | Gerben Roelof Fokkema | Unclassified | IPv6 | 4 |
| AS58299 | Openfactory GmbH | Residential | IPv4 | 2 |
| AS197371 | Andreas Meyer, trading as Swiss VoIP Carrier Solutions Meyer | Unclassified | IPv4 | 2 |
| AS206193 | Jacob Leonard | Unclassified | IPv6 | 2 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 2 |
| AS42 | WoodyNet, Inc. | Unclassified | IPv4 | 1 |
| AS202959 | Lushu Limited | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS47498 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS62000 | SERVERD SAS | Hosting | IPv4 IPv6 | 12 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 10 |
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 10 |
| AS400688 | Daniel Marks, Sole Proprietorship | Unclassified | IPv4 IPv6 | 6 |
| AS56762 | Olympic Input/Output, LLC | Unclassified | IPv6 | 4 |
| AS203405 | Lin Kai-Lun | Unclassified | IPv6 | 4 |
| AS215743 | Gerben Roelof Fokkema | Unclassified | IPv6 | 4 |
| AS58299 | Openfactory GmbH | Residential | IPv4 | 2 |
| AS197371 | Andreas Meyer, trading as Swiss VoIP Carrier Solutions Meyer | Unclassified | IPv4 | 2 |
| AS206193 | Jacob Leonard | Unclassified | IPv6 | 2 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.09M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.