Skip to main content

AS49296

Broadcore

ITS AG

Registry

Authoritative registration data

AS number
49296
Name
Broadcore
Organisation
ITS AG
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS49296
217.148.224.0/20 IPv4 /20 RPKI valid
185.71.4.0/24 IPv4 /24 RPKI valid
185.71.5.0/24 IPv4 /24 not checked
185.71.6.0/24 IPv4 /24 not checked
185.71.7.0/24 IPv4 /24 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 AS49296
Address families
KleyReX: Peering LAN 5,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS49296 in AS paths

Observed upstreams
Families
AS12586 ASGHOSTNET 176 953
v4
AS6939 HURRICANE 34 181
v4
AS25091 IP-Max 6 45
v4
AS22356 ASN22356 8 35
v4
AS14840 ASN14840 2 25
v4
AS3257 GTT-BACKBONE 20 21
v4
AS8298 IPNG 2 10
v4
AS9498 BBIL-AP 1 5
v4
AS212508 LOWHOSTING-AS 1 5
v4
AS263444 ASN263444 1 5
v4
AS286 KPN 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS49296 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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