Skip to main content

AS208444

BIG3AS

Bringe Informationstechnik GmbH

Registry

Authoritative registration data

AS number
208444
Name
BIG3AS
Organisation
Bringe Informationstechnik GmbH
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS208444
185.192.170.0/23 IPv4 /23 not checked
2a06:5d07::/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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS208444 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

19 networks seen before AS208444 in AS paths

Observed upstreams
Families
AS174 COGENT-174 108 126
v4
AS6939 HURRICANE 87 117
v4 v6
AS47372 BIG3AS 49 60
v4
AS9002 RETN-AS 15 19
v6
AS8218 NEO-ASN 2 11
v4 v6
AS34019 HIVANE 4 10
v4 v6
AS5405 INTERDOTLINK 5 8
v4 v6
AS25091 IP-Max 3 8
v4 v6
AS47147 AS-ANX 3 8
v4 v6
AS48362 TKSWF-AS 2 8
v4 v6
AS1764 NEXTLAYER-AS 2 4
v4 v6
AS24961 MYLOC-AS 2 4
v4 v6
AS29222 Infomaniak-AS 2 3
v4 v6
AS34177 CELESTE-AS 2 3
v4 v6
AS33891 CORE-BACKBONE 2 2
v6
AS1836 GREEN 1 2
v4 v6
AS39351 ESAB-AS 1 2
v4 v6
AS4601 DNET 1 1
v6
AS9009 M247 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS208444 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

28 adjacencies that may be an artefact of collector peering

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.