bgpreport

Network · data from 2026-11-12

AS61798 TELECOM PONTONET

Registry name: AS61798 - HIGH TECH TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61798, 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.

200.229.80.0/23 No ROA Nonecovered by 200.229.80.0/22 663 99% 67
2804:1980:1000::/48 No ROA Nonecovered by 2804:1980::/32 636 100% 67
2804:1980:1001::/48 No ROA Nonecovered by 2804:1980::/32 636 100% 67
2804:1980:9000::/47 No ROA Nonecovered by 2804:1980::/32 636 100% 67
2804:1980:9002::/47 No ROA Nonecovered by 2804:1980::/32 636 100% 67
2804:1980:ff00::/40 No ROA Nonecovered by 2804:1980::/32 635 100% 67
200.229.83.0/24 No ROA Other IRR onlyRADB 666 99% 67
200.229.80.0/24 No ROA Other IRR onlyRADB 663 99% 67
200.229.82.0/24 No ROA Other IRR onlyRADB 663 99% 67
200.229.81.0/24 No ROA Other IRR onlyRADB 662 98% 67
2804:1980::/32 No ROA Other IRR onlyRADB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS61798: AS61798. 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 (AS61798 isn't in the set, or no route object for AS61798 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 objectsAS61798 in itNot covered
AS61798 A single AS number, not a set: AS61798 (this network), 6 route objects.

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

  • ROA: none11
  • Route object: none6
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none200.229.80.0/23No ROA covers it. Add a ROA for AS61798, maxLength 23.663 of 673
Route object: none200.229.80.0/23No route object for it. A route object for 200.229.80.0/22 with origin AS61798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61798 in the RIR database for the space.663 of 673
ROA: none2804:1980:1000::/48No ROA covers it. Add a ROA for AS61798, maxLength 48.636 of 636
Route object: none2804:1980:1000::/48No route object for it. A route object for 2804:1980::/32 with origin AS61798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61798 in the RIR database for the space.636 of 636
ROA: none2804:1980:1001::/48No ROA covers it. Add a ROA for AS61798, maxLength 48.636 of 636
Route object: none2804:1980:1001::/48No route object for it. A route object for 2804:1980::/32 with origin AS61798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61798 in the RIR database for the space.636 of 636
ROA: none2804:1980:9000::/47No ROA covers it. Add a ROA for AS61798, maxLength 47.636 of 636
Route object: none2804:1980:9000::/47No route object for it. A route object for 2804:1980::/32 with origin AS61798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61798 in the RIR database for the space.636 of 636
ROA: none2804:1980:9002::/47No ROA covers it. Add a ROA for AS61798, maxLength 47.636 of 636
Route object: none2804:1980:9002::/47No route object for it. A route object for 2804:1980::/32 with origin AS61798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61798 in the RIR database for the space.636 of 636
ROA: none2804:1980:ff00::/40No ROA covers it. Add a ROA for AS61798, maxLength 40.635 of 636
Route object: none2804:1980:ff00::/40No route object for it. A route object for 2804:1980::/32 with origin AS61798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61798 in the RIR database for the space.635 of 636
ROA: none200.229.83.0/24No ROA covers it. Add a ROA for AS61798, maxLength 24.666 of 673
Route object: RIR200.229.83.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none200.229.80.0/24No ROA covers it. Add a ROA for AS61798, maxLength 24.663 of 673
Route object: RIR200.229.80.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
ROA: none200.229.82.0/24No ROA covers it. Add a ROA for AS61798, maxLength 24.663 of 673
Route object: RIR200.229.82.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
ROA: none200.229.81.0/24No ROA covers it. Add a ROA for AS61798, maxLength 24.662 of 673
Route object: RIR200.229.81.0/24Route object only in RADB. Add it in the RIR database for the space.662 of 673
ROA: none2804:1980::/32No ROA covers it. Add a ROA for AS61798, maxLength 32.636 of 636
Route object: RIR2804:1980::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

200.229.80.0/22RADB, TCNo ROA

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.