Observed topology

AS198227 NEWTELECOM-AS

Unclassified RIPE

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS198227: 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
AS48641	Syntegra Telecom LLC	Residential	IPv4	245
AS8772	Netassist International EOOD	Unclassified	IPv4	30
AS50263	A-Systems Sp. z o.o.	Unclassified	IPv4	30
AS24482	SG.GS	Hosting	IPv4	5
AS29632	Netassist International EOOD	Unclassified	IPv4	5
AS34056	Kyiv Optic Networks ltd	Residential	IPv4	5

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS210526	FOP Kovalenko Igor Valentynovych	Unclassified	IPv4	65

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS48641	Syntegra Telecom LLC	Residential	IPv4	291
AS210526	FOP Kovalenko Igor Valentynovych	Unclassified	IPv4	65
AS8772	Netassist International EOOD	Unclassified	IPv4	36
AS50263	A-Systems Sp. z o.o.	Unclassified	IPv4	36
AS34056	Kyiv Optic Networks ltd	Residential	IPv4	10
AS24482	SG.GS	Hosting	IPv4	6
AS29632	Netassist International EOOD	Unclassified	IPv4	6

Provenance

Where this comes from

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