bgpreport

Network · data from 2026-11-12

AS56304 THETOTALTEAM-AS-AP - The Total Team Limited

Registry name: THETOTALTEAM-AS-AP - The Total Team Limited, NZ · not in PeeringDB

24IPv4 routes 79.2% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS56304, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS56304, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
27.121.96.0/22 No ROA RIR databaseAPNIC, RADB 672 100% 68
27.121.96.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 68
27.121.97.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 68
27.121.98.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 68
27.121.99.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 68
103.39.44.0/22 Valid Other IRR onlyRADB 672 100% 68
103.39.44.0/24 Valid Other IRR onlyRADB 672 100% 68
103.39.45.0/24 Valid Other IRR onlyRADB 672 100% 68
103.39.46.0/24 Valid Other IRR onlyRADB 672 100% 68
103.39.47.0/24 Valid Other IRR onlyRADB 672 100% 68
103.15.152.0/22 Valid RIR databaseAPNIC, RADB 672 100% 68
103.15.152.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
103.15.153.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
103.15.154.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
103.15.155.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
103.243.160.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
175.111.100.0/22 Valid RIR databaseAPNIC, RADB 672 100% 68
175.111.100.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
175.111.101.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
175.111.102.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
175.111.103.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
192.156.225.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
202.36.170.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
202.49.187.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
2400:3d80::/32 Valid RIR databaseAPNIC, RADB 636 100% 69
2400:6900::/32 Valid RIR databaseAPNIC, RADB 636 100% 69
2401:9480::/32 Valid RIR databaseAPNIC, RADB 636 100% 69

AS-SET

AS56304 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 19 are in fix.csv.

  • ROA: none5
  • Route object: RIR5
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none27.121.96.0/22No ROA covers it. Add a ROA for AS56304, maxLength 22.672 of 673
ROA: none27.121.96.0/24No ROA covers it. Add a ROA for AS56304, maxLength 24.672 of 673
ROA: none27.121.97.0/24No ROA covers it. Add a ROA for AS56304, maxLength 24.672 of 673
ROA: none27.121.98.0/24No ROA covers it. Add a ROA for AS56304, maxLength 24.672 of 673
ROA: none27.121.99.0/24No ROA covers it. Add a ROA for AS56304, maxLength 24.672 of 673
Route object: RIR103.39.44.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.39.44.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.39.45.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.39.46.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.39.47.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS56304 whose prefix no peer sees AS56304 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.15.152.0/23APNICValid
103.15.154.0/23APNICValid
131.203.63.0/24APNICValid
175.111.100.0/23APNICValid
175.111.102.0/23APNICValid
2400:6900:3010::/48APNICValid
2400:6900:f000::/48APNICValid
2400:6900:ffff::/48APNICValid
2401:9480:300::/40APNICValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.