asn.dev

Observed topology

AS28213 LCI Equipamentos de Informatica LTDA - LCI Telecom

Upstreams 22 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 20
Adjacent (IPv6) 18

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28213: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6239
AS174Cogent Communications, LLCTransitIPv4 IPv6131
AS6939Hurricane Electric LLCTransitIPv4 IPv6117
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv675
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv654
AS22652Videotron LteeResidentialIPv4 IPv627
AS12859BIT BVHostingIPv4 IPv615
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv615
AS1836green.ch AGResidentialIPv4 IPv615
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv615
AS212024Marc SchmittUnclassifiedIPv4 IPv615
AS34019Hivane AssociationUnclassifiedIPv4 IPv615
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv614
AS12779IT.Gate S.p.A.UnclassifiedIPv412
AS20485Joint Stock Company TransTeleComUnclassifiedIPv412
AS37100SEACOM LimitedUnclassifiedIPv412
AS57463NetIX Communications JSCUnclassifiedIPv412
AS12552GlobalConnect ABUnclassifiedIPv412
AS29632Netassist International EOODUnclassifiedIPv66
AS56662Marcin GondekUnclassifiedIPv63
AS213241TECHIT.BE SRLResidentialIPv63

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.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266182FLY PROVEDOR DE INTERNETUnclassifiedIPv4 IPv6212

Adjacency

Adjacent networks

38 shown

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6304
AS266182FLY PROVEDOR DE INTERNETUnclassifiedIPv4 IPv6212
AS174Cogent Communications, LLCTransitIPv4 IPv6163
AS6939Hurricane Electric LLCTransitIPv4 IPv6148
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv694
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv665
AS22652Videotron LteeResidentialIPv4 IPv634
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv619
AS212024Marc SchmittUnclassifiedIPv4 IPv619
AS24482SG.GSHostingIPv4 IPv619
AS1836green.ch AGResidentialIPv4 IPv619
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv619
AS34019Hivane AssociationUnclassifiedIPv4 IPv619
AS12859BIT BVHostingIPv4 IPv618
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv616
AS57463NetIX Communications JSCUnclassifiedIPv415
AS37100SEACOM LimitedUnclassifiedIPv415
AS12552GlobalConnect ABUnclassifiedIPv415
AS20485Joint Stock Company TransTeleComUnclassifiedIPv415
AS12779IT.Gate S.p.A.UnclassifiedIPv415
AS29632Netassist International EOODUnclassifiedIPv68
AS213241TECHIT.BE SRLResidentialIPv64
AS56662Marcin GondekUnclassifiedIPv63

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS28213, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 6 exchanges across 3 countries and 3 regions.

ExchangeLocationTheir addressMember ports
IX.br (PTT.br) São PauloSão Paulo, Brazil187.16.214.1432,690
DE-CIX FrankfurtFrankfurt, Germany80.81.195.711,073
IX.br (PTT.br) FortalezaFortaleza, Brazil45.68.75.209920
DE-CIX New YorkNew York, United States206.82.105.3279
IX.br (PTT.br) BrasíliaBrasília, Brazil45.184.144.94279
IX.br (PTT.br) CuiabáCuiabá, Brazil187.16.203.2359

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.