Observed topology
AS48695 ATHEEB-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS48695: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS47794 | Etihad GO Company For communications | Unclassified | IPv4 IPv6 | 35,368 |
Transit
Downstream networks
Networks for which AS48695 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS44577 | Saudi Energy Company | Unclassified | IPv4 | 314 |
| AS48840 | Perfect Presentation For Commercial Services Company, A Saudi Joint Stock Company | Unclassified | IPv4 IPv6 | 184 |
| AS205695 | Maximum Solutions for Communications and Information Technology LLC | Unclassified | IPv4 | 128 |
| AS31699 | BANK AL JAZIRA | Unclassified | IPv4 | 122 |
| AS43378 | Ministry of Commerce and Industry in Saudi Arabia | Unclassified | IPv4 | 64 |
| AS62415 | Agricultural Development Fund (gov) | Unclassified | IPv4 | 64 |
| AS215557 | Saudi Information Technology Company CJSC | Unclassified | IPv4 | 64 |
| AS61268 | SAUDI TADAWUL GROUP HOLDING COMPANY JSC | Unclassified | IPv4 | 58 |
| AS3573 | Accenture LLP | Unclassified | IPv6 | 37 |
| AS25233 | ARABIAN INTERNET & COMMUNICATIONS SERVICES CO.LTD | Unclassified | IPv4 | 28 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48695 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS47794 | Etihad GO Company For communications | Unclassified | IPv4 IPv6 | 36,466 |
| AS44577 | Saudi Energy Company | Unclassified | IPv4 | 314 |
| AS48840 | Perfect Presentation For Commercial Services Company, A Saudi Joint Stock Company | Unclassified | IPv4 IPv6 | 184 |
| AS205695 | Maximum Solutions for Communications and Information Technology LLC | Unclassified | IPv4 | 128 |
| AS31699 | BANK AL JAZIRA | Unclassified | IPv4 | 122 |
| AS43378 | Ministry of Commerce and Industry in Saudi Arabia | Unclassified | IPv4 | 64 |
| AS62415 | Agricultural Development Fund (gov) | Unclassified | IPv4 | 64 |
| AS215557 | Saudi Information Technology Company CJSC | Unclassified | IPv4 | 64 |
| AS61268 | SAUDI TADAWUL GROUP HOLDING COMPANY JSC | Unclassified | IPv4 | 58 |
| AS3573 | Accenture LLP | Unclassified | IPv6 | 37 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.