Skip to main content

AS213373

IPCONNECT

IP Connect Inc

Registry

Authoritative registration data

AS number
213373
Name
IPCONNECT
Organisation
IP Connect Inc
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

2

Total announced

14

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS213373
109.205.187.0/24 IPv4 /24 not checked
146.19.173.0/24 IPv4 /24 RPKI valid
149.3.170.0/24 IPv4 /24 not checked
164.215.103.0/24 IPv4 /24 RPKI valid
164.215.98.0/24 IPv4 /24 RPKI valid
2.56.10.0/24 IPv4 /24 RPKI valid
45.141.56.0/24 IPv4 /24 RPKI valid
45.141.58.0/24 IPv4 /24 not checked
45.141.59.0/24 IPv4 /24 not checked
46.23.109.0/24 IPv4 /24 not checked
5.178.0.0/24 IPv4 /24 RPKI valid
85.203.26.0/24 IPv4 /24 RPKI valid
2a10:5fc0::/32 IPv6 /32 not checked
2a10:5fc1::/32 IPv6 /32 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS213373
Address families
AMS-IX 100,000 Mbps IPv4 · IPv6
Giganet IXN Amsterdam 100,000 Mbps IPv4 · IPv6
Giganet IXN Warsaw: Warsaw local exchange 100,000 Mbps IPv4 · IPv6
Giganet IXN: Global exchange 100,000 Mbps IPv4 · IPv6
INTERIX 100,000 Mbps IPv4 · IPv6
Speed-IX: SPEED-IX 200,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS213373 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

36 networks seen before AS213373 in AS paths

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS213373 in AS paths

Observed downstreams
Families
AS211922 IPDISTR 630 2,135
v4 v6
AS212558 GLOBALNETSYS 288 386
v4
AS210530 ip2con 271 341
v4

No rows match “”.

Showing – of

Uncertain adjacencies

59 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 55
v4 v6
AS47147 AS-ANX 3 51
v4 v6
AS12779 ITGATE 3 44
v4 v6
AS48185 team_blue 1 36
v4 v6
AS62167 Tismi 3 34
v4 v6
AS25160 VORBOSS 3 30
v4 v6
AS49544 i3Dnet 3 30
v4 v6
AS51184 FONIRA 3 30
v4 v6
AS12859 NL-BIT 3 20
v4 v6
AS8298 IPNG 3 17
v4 v6
AS39122 BLACKNIGHT-AS 3 17
v4 v6
AS41666 PYRO-AS 3 17
v4 v6
AS209823 ENKI-AS 3 17
v4 v6
AS1103 SURFNET-NL 3 16
v4 v6
AS36236 NETACTUATE 3 16
v4 v6
AS48919 UA-CITY-AS 3 16
v4 v6
AS50763 MCKAYCOM 3 16
v4 v6
AS199524 GCORE 3 16
v4 v6
AS559 Switch 3 15
v4 v6
AS680 DFN 3 15
v4 v6
AS1140 SIDN 3 15
v4 v6
AS1828 UNITAS 3 15
v4 v6
AS3333 RIPE-NCC-AS 3 15
v4 v6
AS15605 CONNESI 3 15
v4 v6
AS20932 SIG-ST 3 15
v4 v6
AS25220 GLOBALNOC-AS 3 15
v4 v6
AS29075 IELO 3 15
v4 v6
AS29140 HOSTSERVER-AS 3 15
v4 v6
AS35280 F5 3 15
v4 v6
AS42541 FIBERBY 3 15
v4 v6
AS45489 SLT-GLOBAL 3 15
v4 v6
AS50300 CUSTDC 3 15
v4 v6
AS51185 MAINSTREAMING-AS 3 15
v4 v6
AS51873 AS-ARCADE 3 15
v4 v6
AS56987 AS-ABACLOUDA 3 15
v4 v6
AS61573 ASN61573 3 15
v4 v6
AS199938 NETZWERGE 3 15
v4 v6
AS271253 ASN271253 3 15
v4 v6
AS202365 Chronos 3 13
v4
AS12969 Vodafone_Iceland 3 12
v4
AS13237 LAMBDANET-AS 3 12
v4
AS14630 INVESCO 3 12
v4
AS37721 ORG-VTS1-AFRINIC 3 12
v4
AS49605 DTS-AS 3 12
v4
AS14907 WIKIMEDIA 1 12
v4 v6
AS12637 SEEWEB 3 10
v4 v6
AS28917 Fiord-AS 2 8
v6
AS15547 NETPLUS 2 7
v4 v6
AS8529 OMANTEL-AS 2 6
v6
AS213241 TECHIT 2 4
v6
AS211922 IPDISTR 1 3
v4 v6
AS212483 level86 1 2
v4
AS17639 CONVERGE-AS 1 1
v6
AS56662 EUTPNET 1 1
v6
AS59514 DARNYTSIA-NET 1 1
v4
AS198150 SIACOM-AS 1 1
v4
AS212558 GLOBALNETSYS 1 1
v4
AS212635 AS212635 1 1
v4
AS263152 ASN263152 1 1
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.