bgpreport

Network · data from 2026-11-12

AS154047 IT2-AS-AP - IT Nut Hosting

Registry name: IT2-AS-AP - IT Nut Hosting, BD · not in PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS154047, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS154047, 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.
203.33.238.0/24 Invalid: origin Other origin only 148 22% 53
74.52.3.0/24 Valid Other IRR onlyRADB 671 100% 66
144.79.125.0/24 Valid RIR databaseAPNIC 673 100% 66
144.79.124.0/24 Valid RIR databaseAPNIC 672 100% 67
165.101.188.0/24 Valid RIR databaseAPNIC 672 100% 67
165.101.189.0/24 Valid RIR databaseAPNIC 672 100% 66

AS-SET

AS154047 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 7 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin203.33.238.0/24ROAs covering it name AS834, not AS154047. If AS154047 should announce it, add a ROA for AS154047.148 of 673
Route object: none203.33.238.0/24Route objects for it name AS834. Add a route object with origin AS154047 in the RIR database for the space.148 of 673
Route object: RIR74.52.3.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

103.25.124.0/24APNICNo ROA
144.79.124.0/23APNICValid
165.101.188.0/23APNICValid
2001:df5:db40::/48APNICValid

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.