- AS Info
- Graph v4
- Prefixes v4
- Bogon
- Peers v4
- Whois
- IRR
- Traceroute
AS48325 has not been visible in the global routing table since July 01, 2024
Some of the information displayed is from that time.
Some of the information displayed is from that time.
Company Website:
Company Looking Glass:
Country of Origin:
Prefixes Originated (all): 2
Prefixes Originated (v4): 2
Prefixes Originated (v6): 0
Prefixes Announced (all): 0
Prefixes Announced (v4): 0
Prefixes Announced (v6): 0
RPKI Originated Valid (all): 0 RPKI Originated Valid (v4): 0 RPKI Originated Valid (v6): 0
BGP Peers Observed (all): 2
BGP Peers Observed (v4): 2
BGP Peers Observed (v6): 0
IPs Originated (v4): 0
AS Paths Observed (v4): 0
AS Paths Observed (v6): 0
Average AS Path Length (all): 0.000
Average AS Path Length (v4): 0.000
Average AS Path Length (v6): 0.000
Prefixes Originated (v4): 2
Prefixes Originated (v6): 0
Prefixes Announced (all): 0
Prefixes Announced (v4): 0
Prefixes Announced (v6): 0
RPKI Originated Valid (all): 0 RPKI Originated Valid (v4): 0 RPKI Originated Valid (v6): 0
BGP Peers Observed (all): 2
BGP Peers Observed (v4): 2
BGP Peers Observed (v6): 0
IPs Originated (v4): 0
AS Paths Observed (v4): 0
AS Paths Observed (v6): 0
Average AS Path Length (all): 0.000
Average AS Path Length (v4): 0.000
Average AS Path Length (v6): 0.000
Loading Website Preview...
AS48325 IPv4 Peers
AS48325 IPv4 Peer Count
AS48325 IPv4 Prefixes Announced
AS48325 IPv4 Prefixes Originated
AS48325 IPv4 Route Propagation
Prefix | Description | Visibility |
---|---|---|
Loading Prefixes... |
Prefix | Description |
---|---|
185.137.240.0/22 | |
185.137.243.0/24 |
Bogon Prefixes | ||
---|---|---|
Prefix | Type | Status |
as-block: AS47870 - AS50048 descr: RIPE NCC ASN block remarks: These AS Numbers are assigned to network operators in the RIPE NCC service region. mnt-by: RIPE-NCC-HM-MNT created: 2024-12-06T06:09:56Z last-modified: 2024-12-06T06:09:56Z source: RIPE aut-num: AS48325 as-name: BazTel org: ORG-BL242-RIPE remarks: +-----------------------------------------------------+-----------+ remarks: | BazTel's Network | AS48325 | remarks: +-----------------------------------------------------+-----------+ remarks: | | remarks: | BazTel operates an open peering policy | remarks: | | remarks: | Operations contact: noc at baztel.co.uk | remarks: | Abuse complaints: abuse at baztel.co.uk | remarks: | Peering requests: peering at baztel.co.uk | remarks: | Corporate Website: https://www.baztel.co.uk | remarks: | | remarks: | PLEASE ENSURE ABUSE REQUESTS ARE SENT TO THE CORRECT ADDRESS ! | remarks: | | remarks: +-----------------------------------------------------------------+ remarks: | | remarks: | We advertise the AS-BAZTEL and AS-BAZTEL-V6 at all locations. | remarks: | | remarks: +-----------------------------------------------------------------+ remarks: | Communities Configurations | remarks: +-----------------------------------------------------------------+ remarks: | Route Types (R) | Location Identifiers (LI) | remarks: +-----------------------------------------------------------------+ remarks: | - 1 Transit Provider | - 21 London 1 (THN) | remarks: | - 2 Exchange Peering (RS) | | remarks: | - 3 Exchange Peering (Direct) | | remarks: | - 4 Private Peering | | remarks: | - 5 Customer Routes | | remarks: +-----------------------------------------------------------------+ remarks: | Provider Identifier (PI) | Generic High Level | remarks: +-----------------------------------------------------------------+ remarks: | - 01 Jump Networks | 48325:100 Transit Provider | remarks: | - | 48325:200 Exchange Peering (RS)| remarks: | - 04 ICUK | 48325:300 Exchange Peering (Di)| remarks: | - 11 Level(3) | 48325:400 Private Peering | remarks: | - 12 NTT | 48325:500 Customer Routes | remarks: | - 16 Telia | 48325:9(LI) Learnt Location | remarks: | - 18 Cogent | | remarks: | - 50 Transit Customers | | remarks: +-----------------------------------------------------------------+ remarks: | Community Construction | remarks: +-----------------------------------------------------------------+ remarks: | We construct communities based on the above values as follows: | remarks: | | remarks: | - (R)(LI)(PI) | remarks: | For example, a route from a transit provider, learnt in | remarks: | London 1, and the provider being Jump Networks would look | remarks: | as follows: 48325:12101 | remarks: | | remarks: | - That same route would also be tagged with the transit | remarks: | provider community (48325:100) and the high level | remarks: | location learnt community (48325:921) | remarks: | | remarks: | Please feel free to contact us for further clarification. | remarks: +-----------------------------------------------------------------+ remarks: | Transit Networks | remarks: +-----------------------------------------------------------------+ remarks: AS8943: Jump Networks mp-import: from AS8943 action pref=90; accept AS-JUMP mp-import: from AS8943 action pref=40; accept ANY mp-export: to AS8943 announce AS-BAZTEL remarks: AS51561: ICuk mp-import: from AS51561 action pref=90; accept AS-ICUK mp-import: from AS51561 action pref=40; accept ANY mp-export: to AS51561 announce AS-BAZTEL remarks: +-----------------------------------------------------------------+ remarks: | Customer Networks | remarks: +-----------------------------------------------------------------+ remarks: AS44749: Pinnacom mp-import: from AS44749 action pref=999; accept AS-PINNACOM mp-import: from AS44749 action pref=999; accept AS-PINNACOM mp-export: to AS44749 announce AS-BAZTEL AND ANY remarks: AS203676: Pinnacom mp-import: from AS203676 action pref=999; accept AS-PINNACOM mp-import: from AS203676 action pref=999; accept AS-PINNACOM mp-export: to AS203676 announce AS-BAZTEL AND ANY remarks: +-----------------------------------------------------------------+ remarks: | Peering Networks | remarks: +-----------------------------------------------------------------+ mp-import: from AS786 action pref=100; accept AS-JANETPLUS mp-export: to AS786 announce AS-BAZTEL mp-import: from AS31631 action pref=100; accept AS31631 mp-export: to AS31631 announce AS-BAZTEL mp-import: from AS29611 action pref=100; accept AS-ELITE mp-export: to AS29611 announce AS-BAZTEL remarks: +-----------------------------------------------------------------+ remarks: For all direct peering sessions we announce AS-BAZTEL & AS-BAZTEL-V6. remarks: We accept members appropriate AS-SET. remarks: +-----------------------------------------------------+-----------+ remarks: | BazTel's Network | AS48325 | remarks: +-----------------------------------------------------+-----------+ remarks: | | remarks: | BazTel operates an open peering policy | remarks: | | remarks: | Operations contact: noc at baztel.co.uk | remarks: | Abuse complaints: abuse at baztel.co.uk | remarks: | Peering requests: peering at baztel.co.uk | remarks: | Corporate Website: https://www.baztel.co.uk | remarks: | | remarks: | PLEASE ENSURE ABUSE REQUESTS ARE SENT TO THE CORRECT ADDRESS ! | remarks: | | remarks: +-----------------------------------------------------------------+ admin-c: JCM295-RIPE tech-c: JCM295-RIPE status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-by: uk-baztel2-1-mnt created: 2019-03-12T10:47:06Z last-modified: 2019-07-03T22:34:09Z source: RIPE organisation: ORG-BL242-RIPE org-name: BazTel Ltd country: GB org-type: LIR address: 9 farmfields rise, woore address: Cw3 9sz address: Cheshire address: UNITED KINGDOM phone: +447471438896 admin-c: BL5790-RIPE tech-c: JCM295-RIPE abuse-c: AR35305-RIPE mnt-ref: uk-baztel2-1-mnt mnt-ref: RIPE-NCC-HM-MNT mnt-by: RIPE-NCC-HM-MNT mnt-by: uk-baztel2-1-mnt created: 2016-02-08T08:42:11Z last-modified: 2024-07-30T13:58:25Z source: RIPE # Filtered person: John C Mason address: TFM24, Telehouse Docklands North phone: +442035198193 nic-hdl: JCM295-RIPE mnt-by: MNT-PINNACOM created: 2016-05-10T23:36:45Z last-modified: 2016-05-10T23:36:45Z source: RIPE
RIPE
aut-num: AS48325
as-name: BazTel
org: ORG-BL242-RIPE
remarks: +-----------------------------------------------------+-----------+
remarks: | BazTel's Network | AS48325 |
remarks: +-----------------------------------------------------+-----------+
remarks: | |
remarks: | BazTel operates an open peering policy |
remarks: | |
remarks: | Operations contact: noc at baztel.co.uk |
remarks: | Abuse complaints: abuse at baztel.co.uk |
remarks: | Peering requests: peering at baztel.co.uk |
remarks: | Corporate Website: https://www.baztel.co.uk |
remarks: | |
remarks: | PLEASE ENSURE ABUSE REQUESTS ARE SENT TO THE CORRECT ADDRESS ! |
remarks: | |
remarks: +-----------------------------------------------------------------+
remarks: | |
remarks: | We advertise the AS-BAZTEL and AS-BAZTEL-V6 at all locations. |
remarks: | |
remarks: +-----------------------------------------------------------------+
remarks: | Communities Configurations |
remarks: +-----------------------------------------------------------------+
remarks: | Route Types (R) | Location Identifiers (LI) |
remarks: +-----------------------------------------------------------------+
remarks: | - 1 Transit Provider | - 21 London 1 (THN) |
remarks: | - 2 Exchange Peering (RS) | |
remarks: | - 3 Exchange Peering (Direct) | |
remarks: | - 4 Private Peering | |
remarks: | - 5 Customer Routes | |
remarks: +-----------------------------------------------------------------+
remarks: | Provider Identifier (PI) | Generic High Level |
remarks: +-----------------------------------------------------------------+
remarks: | - 01 Jump Networks | 48325:100 Transit Provider |
remarks: | - | 48325:200 Exchange Peering (RS)|
remarks: | - 04 ICUK | 48325:300 Exchange Peering (Di)|
remarks: | - 11 Level(3) | 48325:400 Private Peering |
remarks: | - 12 NTT | 48325:500 Customer Routes |
remarks: | - 16 Telia | 48325:9(LI) Learnt Location |
remarks: | - 18 Cogent | |
remarks: | - 50 Transit Customers | |
remarks: +-----------------------------------------------------------------+
remarks: | Community Construction |
remarks: +-----------------------------------------------------------------+
remarks: | We construct communities based on the above values as follows: |
remarks: | |
remarks: | - (R)(LI)(PI) |
remarks: | For example, a route from a transit provider, learnt in |
remarks: | London 1, and the provider being Jump Networks would look |
remarks: | as follows: 48325:12101 |
remarks: | |
remarks: | - That same route would also be tagged with the transit |
remarks: | provider community (48325:100) and the high level |
remarks: | location learnt community (48325:921) |
remarks: | |
remarks: | Please feel free to contact us for further clarification. |
remarks: +-----------------------------------------------------------------+
remarks: | Transit Networks |
remarks: +-----------------------------------------------------------------+
remarks: AS8943: Jump Networks
mp-import: from AS8943 action pref=90; accept AS-JUMP
mp-import: from AS8943 action pref=40; accept ANY
mp-export: to AS8943 announce AS-BAZTEL
remarks: AS51561: ICuk
mp-import: from AS51561 action pref=90; accept AS-ICUK
mp-import: from AS51561 action pref=40; accept ANY
mp-export: to AS51561 announce AS-BAZTEL
remarks: +-----------------------------------------------------------------+
remarks: | Customer Networks |
remarks: +-----------------------------------------------------------------+
remarks: AS44749: Pinnacom
mp-import: from AS44749 action pref=999; accept AS-PINNACOM
mp-import: from AS44749 action pref=999; accept AS-PINNACOM
mp-export: to AS44749 announce AS-BAZTEL AND ANY
remarks: AS203676: Pinnacom
mp-import: from AS203676 action pref=999; accept AS-PINNACOM
mp-import: from AS203676 action pref=999; accept AS-PINNACOM
mp-export: to AS203676 announce AS-BAZTEL AND ANY
remarks: +-----------------------------------------------------------------+
remarks: | Peering Networks |
remarks: +-----------------------------------------------------------------+
mp-import: from AS786 action pref=100; accept AS-JANETPLUS
mp-export: to AS786 announce AS-BAZTEL
mp-import: from AS31631 action pref=100; accept AS31631
mp-export: to AS31631 announce AS-BAZTEL
mp-import: from AS29611 action pref=100; accept AS-ELITE
mp-export: to AS29611 announce AS-BAZTEL
remarks: +-----------------------------------------------------------------+
remarks: For all direct peering sessions we announce AS-BAZTEL & AS-BAZTEL-V6.
remarks: We accept members appropriate AS-SET.
remarks: +-----------------------------------------------------+-----------+
remarks: | BazTel's Network | AS48325 |
remarks: +-----------------------------------------------------+-----------+
remarks: | |
remarks: | BazTel operates an open peering policy |
remarks: | |
remarks: | Operations contact: noc at baztel.co.uk |
remarks: | Abuse complaints: abuse at baztel.co.uk |
remarks: | Peering requests: peering at baztel.co.uk |
remarks: | Corporate Website: https://www.baztel.co.uk |
remarks: | |
remarks: | PLEASE ENSURE ABUSE REQUESTS ARE SENT TO THE CORRECT ADDRESS ! |
remarks: | |
remarks: +-----------------------------------------------------------------+
admin-c: DUMY-RIPE
tech-c: DUMY-RIPE
status: ASSIGNED
mnt-by: RIPE-NCC-END-MNT
mnt-by: uk-baztel2-1-mnt
created: 2019-03-12T10:47:06Z
last-modified: 2019-07-03T22:34:09Z
source: RIPE
remarks: ****************************
remarks: * THIS OBJECT IS MODIFIED
remarks: * Please note that all data that is generally regarded as personal
remarks: * data has been removed from this object.
remarks: * To view the original object, please query the RIPE Database at:
remarks: * http://www.ripe.net/whois
remarks: ****************************
Loading probes...
Select Probe | ||||
---|---|---|---|---|
Type | Name | ASN | IP | City |
⏳
Results will appear here.