asn.dev

Observed topology

AS6412 KW KEMS Block-A, Floor 7, Souq Al-Kabeer Kuwait City, State of Kuwait P O Box 3623, Safat 13037 KW

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6412: 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
AS42961Mobile Telecommunications Company K.S.C.P.ResidentialIPv47,348
AS43852Fast Communication Company LtdUnclassifiedIPv47,042
AS42156GNX B.V.UnclassifiedIPv4120
AS59796StormWall s.r.o.UnclassifiedIPv473

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS42781Zajil International Telecom Company KSCCUnclassifiedIPv42,111
AS201378Zajil International Telecom Company KSCCUnclassifiedIPv4236
AS196921Wireless Mobile Data Company KSCCUnclassifiedIPv4177
AS7862Chevron CorporationUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS42961Mobile Telecommunications Company K.S.C.P.ResidentialIPv410,164
AS43852Fast Communication Company LtdUnclassifiedIPv48,786
AS42781Zajil International Telecom Company KSCCUnclassifiedIPv44,147
AS201378Zajil International Telecom Company KSCCUnclassifiedIPv4236
AS196921Wireless Mobile Data Company KSCCUnclassifiedIPv4177
AS42156GNX B.V.UnclassifiedIPv4122
AS59796StormWall s.r.o.UnclassifiedIPv473
AS7862Chevron CorporationUnclassifiedIPv42

Provenance

Where this comes from

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