bgpreport

Network · data from 2026-11-12

AS152455 THREEDOTNET-AS-AP - THREE DOT NET

Registry name: THREEDOTNET-AS-AP - THREE DOT NET, BD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS152455, 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.
2001:df6:1c0::/49 Invalid: maxLength Nonecovered by 2001:df6:1c0::/48 0 0%low visibility 1
2001:df6:1c0:8000::/49 Invalid: maxLength Nonecovered by 2001:df6:1c0::/48 0 0%low visibility 1
157.15.114.0/24 Valid RIR databaseAPNIC 673 100% 69
157.15.115.0/24 Valid RIR databaseAPNIC 672 100% 67
2001:df6:1c0::/48 Valid RIR databaseAPNIC 635 100% 69

AS-SET

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

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2001:df6:1c0::/49ROA 2001:df6:1c0::/48 AS152455 has maxLength 48; the route is a /49. Raise the maxLength, or add a ROA for 2001:df6:1c0::/49.0 of 636
Route object: none2001:df6:1c0::/49No route object for it. A route object for 2001:df6:1c0::/48 with origin AS152455 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS152455 in the RIR database for the space.0 of 636
ROA: maxLength2001:df6:1c0:8000::/49ROA 2001:df6:1c0::/48 AS152455 has maxLength 48; the route is a /49. Raise the maxLength, or add a ROA for 2001:df6:1c0:8000::/49.0 of 636
Route object: none2001:df6:1c0:8000::/49No route object for it. A route object for 2001:df6:1c0::/48 with origin AS152455 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS152455 in the RIR database for the space.0 of 636

Route objects not announced

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

157.15.114.0/23APNICValid

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.