bgpreport

Network · data from 2026-11-12

AS133210 EN Technologies

Registry name: ENTECHNOLOGIES-AS-AP - EN Technologies Pte Ltd, SG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133210, 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.
103.120.207.0/24 Valid Other origin only 669 99% 67
82.21.215.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
82.21.231.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
82.22.229.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
82.24.222.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
82.26.228.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
82.29.223.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
103.112.80.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
103.176.59.0/24 Valid RIR databaseAPNIC 669 99% 67
103.253.24.0/24 Valid RIR databaseAPNIC 669 99% 67
103.253.25.0/24 Valid RIR databaseAPNIC 669 99% 67
103.253.26.0/24 Valid RIR databaseAPNIC 669 99% 67
103.253.27.0/24 Valid RIR databaseAPNIC 669 99% 67
103.255.250.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
167.253.47.0/24 Valid RIR databaseARIN 669 99% 67
194.15.115.0/24 Valid RIR databaseRIPE 669 99% 67
194.26.18.0/24 Valid RIR databaseRIPE 669 99% 67
2602:fac2:8::/48 Valid RIR databaseARIN 635 100% 67
2001:df0:940::/48 Valid RIR databaseAPNIC 634 100% 70
2001:df1:a800::/48 Valid RIR databaseAPNIC, RADB 634 100% 70
2a0d:5140::/32 Valid RIR databaseRIPE 634 100% 70

AS-SET

PeeringDB's irr_as_set for AS133210: AS-ENTECHNOLOGIES. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS133210 isn't in the set, or no route object for AS133210 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS133210 in itNot covered
AS-ENTECHNOLOGIES APNIClists itself further down2 member sets in no database: AS139989:AS-ALL, AS150249:AS-ATHARVA 316157,745 Yes 1

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.

  • Route object: none1
  • AS-SET: missing member2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none103.120.207.0/24Route objects for it name AS137373. Add a route object with origin AS133210 in the RIR database for the space.669 of 673
AS-SET: missing memberAS-ENTECHNOLOGIESAS-ENTECHNOLOGIES (APNIC) lists AS139989:AS-ALL; no IRR database read has it.
AS-SET: missing memberAS-ENTECHNOLOGIESAS-ENTECHNOLOGIES (APNIC) lists AS150249:AS-ATHARVA; no IRR database read has it.

Route objects not announced

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

2001:470:1c6::/48ARINInvalid: origin
2001:470:39f::/48ARINInvalid: origin

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.