bgpreport

Network · data from 2026-11-12

AS142400 IDTEL

Registry name: IDNIC-IDT-AS-ID - PT Inovasi Digital Telekomunikasi, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS142400, 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:df7:ab80::/48 No ROA Other IRR onlyRADB 632 99% 70
103.172.186.0/24 Valid Other IRR onlyRADB 673 100% 69
103.172.187.0/24 Valid Other IRR onlyRADB 673 100% 69

AS-SET

PeeringDB's irr_as_set for AS142400: AS142400:AS-IDT-ID. 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 (AS142400 isn't in the set, or no route object for AS142400 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 objectsAS142400 in itNot covered
AS142400:AS-IDT-ID In no IRR database read today.

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

  • ROA: none1
  • Route object: RIR3
  • AS-SET: not found1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2001:df7:ab80::/48No ROA covers it. Add a ROA for AS142400, maxLength 48.632 of 636
Route object: RIR2001:df7:ab80::/48Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR103.172.186.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.172.187.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
AS-SET: not foundAS142400:AS-IDT-IDPeeringDB names AS142400:AS-IDT-ID; no IRR database read has it.

Route objects not announced

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

103.172.186.0/23RADBValid

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.