asn.dev

Observed topology

AS12556 Internet Solutions (Kenya) - Internet Solutions (Kenya)

Unclassified AFRINIC

Upstreams 1 carry this network
Downstreams 7 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 0
Upstream graph Who carries AS12556, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS12556 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS15808IDDQD-ASUnclassifiedIPv4603

Transit

Downstream networks

inferred

Networks for which AS12556 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS328754DIAMOND TRUST BANK UGANDA LIMITEDUnclassifiedIPv4198
AS328883Diamond Trust Bank Kenya LimitedUnclassifiedIPv4125
AS328477African Banking Corporation LimitedUnclassifiedIPv468
AS328705Victoria Commercial Bank LimitedUnclassifiedIPv468
AS13150CATO NETWORKS LTDUnclassifiedIPv426
AS328292AGENT BANKING COMPANY OF UGANDAUnclassifiedIPv49
AS328836SIDIAN BANK LIMITEDUnclassifiedIPv42

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS12556 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS15808IDDQD-ASUnclassifiedIPv41,089
AS328754DIAMOND TRUST BANK UGANDA LIMITEDUnclassifiedIPv4198
AS328883Diamond Trust Bank Kenya LimitedUnclassifiedIPv4125
AS328477African Banking Corporation LimitedUnclassifiedIPv468
AS328705Victoria Commercial Bank LimitedUnclassifiedIPv468
AS13150CATO NETWORKS LTDUnclassifiedIPv426
AS3741Dimension DataUnclassifiedIPv410
AS328292AGENT BANKING COMPANY OF UGANDAUnclassifiedIPv49
AS328836SIDIAN BANK LIMITEDUnclassifiedIPv42

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.