Observed topology

AS6769 SICN Kertinis valstybes telekomunikaciju centras

Unclassified RIPE

Upstreams 5 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 3

Upstream graph Who carries AS6769, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS6769 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6769: 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
AS13194	UAB "Bite Lietuva"	Unclassified	IPv4 IPv6	496
AS12578	SIA Tet	Residential	IPv4 IPv6	210
AS6939	Hurricane Electric LLC	Transit	IPv4	91
AS3303	Swisscom (Schweiz) AG	Residential	IPv4	13
AS1257	Tele2 Sverige AB	Mobile	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS207186	Kauno Technologijos Universitetas	Unclassified	IPv4 IPv6	76
AS196852	Valstybine ligoniu kasa prie Sveikatos apsaugos ministerijos	Unclassified	IPv4	60
AS8764	Telia Lietuva, AB	Residential	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS13194	UAB "Bite Lietuva"	Unclassified	IPv4 IPv6	577
AS12578	SIA Tet	Residential	IPv4 IPv6	253
AS6939	Hurricane Electric LLC	Transit	IPv4	100
AS207186	Kauno Technologijos Universitetas	Unclassified	IPv4 IPv6	76
AS196852	Valstybine ligoniu kasa prie Sveikatos apsaugos ministerijos	Unclassified	IPv4	60
AS3303	Swisscom (Schweiz) AG	Residential	IPv4	15
AS1257	Tele2 Sverige AB	Mobile	IPv4	5
AS8764	Telia Lietuva, AB	Residential	IPv4	1

Provenance

Where this comes from

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