Skip to main content

AS44908

MANG_AS

ORG-MG357-RIPE

Registry

Authoritative registration data

AS number
44908
Name
MANG_AS
Organisation
ORG-MG357-RIPE
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

6

Total announced

6

Announced prefixes

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

Prefixes announced by AS44908
2a13:aac4:1800::/37 IPv6 /37 RPKI valid
2a0a:280:3600::/40 IPv6 /40 not checked
2a0a:280:3640::/44 IPv6 /44 RPKI valid
2a0a:280:3650::/44 IPv6 /44 RPKI valid
2a0a:280:3660::/44 IPv6 /44 RPKI valid
2a0f:9400:6908::/48 IPv6 /48 RPKI valid

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 AS44908
Address families
FogIXP 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 AS44908 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS44908 in AS paths

Observed upstreams
Families
AS47152 Fibersix 133 727
v6
AS214675 Starlamp 113 274
v6
AS39351 ESAB-AS 1 2
v6
AS205794 RTTW-AS 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS44908 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS34927 iFog-GmbH 1 2
v6
AS58299 OPENFACTORY-AS 1 2
v6

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.