bgpreport

Network · data from 2026-11-12

AS133817 Inti Data Telematika

Registry name: INTIDATA-AS-ID - PT Inti Data Telematika, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133817, 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.53.77.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.53.79.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.187.215.0/24 Valid Other IRR onlyRADB 673 100% 69
103.187.214.0/24 Valid Other IRR onlyRADB 672 100% 69
103.53.78.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
2402:5580::/32 Valid Other IRR onlyRADB 635 100% 69
103.53.76.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69

AS-SET

PeeringDB's irr_as_set for AS133817: AS133817:AS-INTINET. 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 (AS133817 isn't in the set, or no route object for AS133817 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 objectsAS133817 in itNot covered
AS133817:AS-INTINET APNIC 16124 No 7

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

  • Route object: RIR6
  • AS-SET: own ASN1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR103.53.77.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.53.79.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.187.215.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.187.214.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.53.78.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2402:5580::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: own ASNAS133817:AS-INTINETAS133817 isn't in AS133817:AS-INTINET (APNIC) once expanded. Add AS133817 to it.

Route objects not announced

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

103.53.76.0/22APNIC, NTTCOM, RADBValid
103.53.76.0/23NTTCOM, RADBValid
103.53.78.0/23NTTCOM, RADBValid
103.187.214.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.