Skip to main content

AS212415

BRECHT-AS

==========================================

Registry

Authoritative registration data

AS number
212415
Name
BRECHT-AS
Organisation
==========================================
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS212415
193.104.187.0/24 IPv4 /24 not checked
194.153.85.0/24 IPv4 /24 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 AS212415
Address families
4b42 Internet Exchange Point: Switzerland — IPv4 · IPv6
KleyReX: Peering LAN 100 Mbps IPv4 · IPv6
LOCIX FRANKFURT: Peering LAN 1,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 AS212415 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS212415 in AS paths

Observed upstreams
Families
AS11967 HOP179 243 590
v4
AS6939 HURRICANE 25 56
v4
AS25091 IP-Max 5 18
v4
AS14840 ASN14840 2 10
v4
AS212508 LOWHOSTING-AS 1 2
v4
AS263444 ASN263444 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS212415 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

10 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.