Skip to main content

AS198408

EMOUSE-NET

E-MOUSE Karol Urbanowicz

Registry

Authoritative registration data

AS number
198408
Name
EMOUSE-NET
Organisation
E-MOUSE Karol Urbanowicz
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

5

Total announced

7

Announced prefixes

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

Prefixes announced by AS198408
195.245.104.0/23 IPv4 /23 not checked
77.65.189.0/24 IPv4 /24 not checked
2a02:f7f:4::/46 IPv6 /46 not checked
2a02:f7f:4::/48 IPv6 /48 not checked
2a02:f7f:5::/48 IPv6 /48 not checked
2a02:f7f:6::/48 IPv6 /48 not checked
2a02:f7f:7::/48 IPv6 /48 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 AS198408
Address families
BGP.Exchange - Berlin 1,000 Mbps IPv6
BGP.Exchange - London 1,000 Mbps IPv6
BGP.Exchange - New York 1,000 Mbps IPv6
EPIX.Warszawa 10,000 Mbps IPv4 · IPv6
EVIX: Peering LAN 1,000 Mbps 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 AS198408 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS198408 in AS paths

Observed upstreams
Families
AS212895 ROUTE64_ORG 332 1,727
v6
AS6939 HURRICANE 179 490
v4
AS3356 LEVEL3 51 138
v4
AS12741 41 108
v4
AS62081 7 14
v4
AS9141 AS9141 4 8
v4
AS201054 4 8
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS198408 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 8
v4
AS215628 1 5
v6
AS49544 i3Dnet 1 4
v4
AS36236 NETACTUATE 1 2
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.