AwanCerahBGP
Home/Japan/AS55374
Autonomous System

FUJITSU LIMITED

AS55374JapanAPNIC · since 2010

FJcloud-East

IPv4 prefixes
133
76,544 addresses
IPv6 prefixes
4
Connectivity
2
2 upstream · 0 peer · 0 downstream
Customer cone
1
networks behind this AS

Route propagation

From AS paths seen by route collectors, up to the first Tier 1 network. Arrow weight follows the number of paths.

Upstream share

AS2510 FUJITSU LIMITED: 53.3%AS2516 KDDI CORPORATION: 46.7%2upstream

Prefix history

IPv4IPv6
050100150Dec 25Jan 26FebMarAprMayJunJulAugSepOctNov18 Nov 2025: 99 IPv42 Dec 2025: 99 IPv416 Dec 2025: 102 IPv430 Dec 2025: 129 IPv413 Jan 2026: 129 IPv427 Jan 2026: 129 IPv410 Feb 2026: 129 IPv424 Feb 2026: 129 IPv410 Mar 2026: 128 IPv424 Mar 2026: 128 IPv47 Apr 2026: 128 IPv421 Apr 2026: 128 IPv45 May 2026: 128 IPv419 May 2026: 128 IPv42 Jun 2026: 128 IPv416 Jun 2026: 128 IPv430 Jun 2026: 128 IPv414 Jul 2026: 128 IPv428 Jul 2026: 128 IPv411 Aug 2026: 128 IPv425 Aug 2026: 127 IPv48 Sep 2026: 122 IPv422 Sep 2026: 120 IPv46 Oct 2026: 120 IPv420 Oct 2026: 120 IPv43 Nov 2026: 96 IPv417 Nov 2026: 96 IPv418 Nov 2025: 2 IPv62 Dec 2025: 2 IPv616 Dec 2025: 4 IPv630 Dec 2025: 4 IPv613 Jan 2026: 4 IPv627 Jan 2026: 4 IPv610 Feb 2026: 4 IPv624 Feb 2026: 4 IPv610 Mar 2026: 4 IPv624 Mar 2026: 4 IPv67 Apr 2026: 4 IPv621 Apr 2026: 4 IPv65 May 2026: 4 IPv619 May 2026: 4 IPv62 Jun 2026: 4 IPv616 Jun 2026: 4 IPv630 Jun 2026: 4 IPv614 Jul 2026: 4 IPv628 Jul 2026: 4 IPv611 Aug 2026: 4 IPv625 Aug 2026: 4 IPv68 Sep 2026: 4 IPv622 Sep 2026: 4 IPv66 Oct 2026: 4 IPv620 Oct 2026: 4 IPv63 Nov 2026: 4 IPv617 Nov 2026: 4 IPv6

Prefixes seen by at least half of the full-table feeds.

D54
BGP reportPoor · see details and how to improve

Live from AwanCerah

Realtime

The route AwanCerah's international router uses right now, and every change, straight from the BGP session.

Log in to view

Rankings

  • #88
    IPv4 spacein Japan
  • #2,397
    IPv4 spaceworldwide

Network profile

Registry
APNIC · JP
Allocated
18 Jan 2010
IX
0
Facilities
0

This network is not in PeeringDB.