Observed topology
AS12556 Internet Solutions (Kenya) - Internet Solutions (Kenya)
Unclassified AFRINIC
Transit
Upstream networks
Networks observed carrying traffic for AS12556: 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.
Transit
Downstream networks
Networks for which AS12556 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS328754 | DIAMOND TRUST BANK UGANDA LIMITED | Unclassified | IPv4 | 195 |
| AS328883 | Diamond Trust Bank Kenya Limited | Unclassified | IPv4 | 129 |
| AS328477 | African Banking Corporation Limited | Unclassified | IPv4 | 67 |
| AS328705 | Victoria Commercial Bank Limited | Unclassified | IPv4 | 67 |
| AS13150 | CATO NETWORKS LTD | Unclassified | IPv4 | 26 |
| AS328292 | AGENT BANKING COMPANY OF UGANDA | Unclassified | IPv4 | 8 |
| AS328836 | SIDIAN BANK LIMITED | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12556 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS15808 | IDDQD-AS | Unclassified | IPv4 | 1,053 |
| AS328754 | DIAMOND TRUST BANK UGANDA LIMITED | Unclassified | IPv4 | 195 |
| AS328883 | Diamond Trust Bank Kenya Limited | Unclassified | IPv4 | 129 |
| AS328477 | African Banking Corporation Limited | Unclassified | IPv4 | 67 |
| AS328705 | Victoria Commercial Bank Limited | Unclassified | IPv4 | 67 |
| AS3741 | Dimension Data | Unclassified | IPv4 | 34 |
| AS13150 | CATO NETWORKS LTD | Unclassified | IPv4 | 26 |
| AS328292 | AGENT BANKING COMPANY OF UGANDA | Unclassified | IPv4 | 8 |
| AS328836 | SIDIAN BANK LIMITED | Unclassified | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.