Your IP address is 44.220.249.141
Please select your question category
Search FAQs
All FAQs
View all frequently asked questions
Tags
View FAQ Tags
Billing

AFRINIC membership and resources related billing FAQs.

WHOIS Database

AFRINIC WHOIS related FAQs
General Queries

General FAQs related to AFRINIC activites
MyAFRINIC

MyAFRINIC portal related FAQs
Membership and Resource Request

Membership related queries

AFRINIC member

FAQ for Existing members
BPKI

AFRINIC BPKI Services
IPv4 Exhaustion

FAQs related to IPv4 Exhaustion and its impact on AFRINIC
FAQs - AFRINIC member

FAQ for Existing members

What is myAFRINIC?

MyAFRINIC is a web-based portal designed for AFRINIC members to manage their contact information, resources, billing and support requests through a simple, graphical, user-friendly interface.

What can I do through myAFRINIC?

Specifically, an AFRINIC member will be able to :-
- Update its organisation's contact details
- Keep the personal profile of the registered contacts up-to-date
- View the organisation's  billing history
- View or download invoices
- Settle invoices via the online payment portal
- Manage AS Numbers
- Manage IPv4 resources
- Manage IPv6 resources
- Create, modify or delete reverse delegations
- Track the status of support tickets

How can I access myafrinic?

The portal is accessible via https://my.afrinic.net. Only registered contacts of AFRINIC members are allowed access to this portal. A login and password is needed(login credentials)

What is a registered contact?

A registered contact is a person whose contact information have been provided by the organisation(Administrative, Technical or Billing) and considered to be the representative of the organisation in our databases. AFRINIC will only attend to service requests originated from the organisation's registered contacts.

How do I become a registered contact for my organisation?

You must either be introduced by an existing registered contact of your organisation (details required are name, address, e-mail and phone number or nic-hdl) or
You can contact MyAFRINIC support staff at myafrinic-activate@afrinic.net who will ask you for verification information before adding you in as a contact.

All the registered contacts of my organisation have left. What should I do?

You should send your request to hostmaster@afrinic.net . The process will then be explained by the AFRINIC hostmasters.

What are my login credentials for the myAFRINIC portal?

You will need a username and a password. The username is the nic-hdl of the registered contact.

What is a nic-hdl?

A nic-hdl is representative of the following details of a person(name, address, telephone number and email).

How do I get/create a nic-hdl?

The step-by-step guide  is available here  .

I have forgotten my nic-hdl. What should I do?

Please query AFRINIC whois database using your e-mail address or your full name in the query field.

What is an Assignment? What is it used for?

 An assignment  refers to the range of IP addresses that an AFRINIC member will use from allocation given by AFRINIC for the following purpose:-

- An end-site or customer with 4 or more IP addresses
- A subnet for the organisation's own network infrastructure
- Any range from which IPs are dynamically assigned

 

What is an allocation or PA (Provider Aggregatable) IP space?

PA space is what has been allocated to LIRs from which they can assign or sub-allocate to end-users / downstream networks as non-portable block. If the end-user / downstream network changes provider, the address space assigned or sub-allocated by the previous service provider (LIR) should be returned and the network renumbered.

What is an Assignment or PI (Provider Independent) IP space?

 Provider-Independent (PI) addresses are globally-unique addresses which :-

- are not assigned by a transit provider

- cannot be aggregated

- can only be assigned by a Regional Internet Registry(RIR)

- cannot be sub-allocated to another entity

 

What is a sub-allocation? What is it used for?

A sub-allocation is   a block of IP address space given by an LIR  to ISPs (LIR's customers) for the purpose of subsequent distribution.

What is reverse delegation? what is it used for?

Reverse delegation is reverse DNS record which map an IP address to a name. It is usually maintained by the organisation who receives direct allocations from an RIR. Reverse delegation is achieved by use of the special domain names in-addr.arpa (IPv4) and ip6.arpa (IPv6). It is usually used to validate a forward DNS record, make network troubleshooting more user friendly by providing names instead of IP addresses and also as part of e-mail anti-spam best practices.

Display #
Page 1 of 3

Profile Information

Application afterLoad: 0.002 seconds, 0.71 MB
Application afterInitialise: 0.058 seconds, 2.72 MB
Application afterRoute: 0.101 seconds, 5.95 MB
Application afterDispatch: 0.144 seconds, 7.04 MB
Application afterRender: 0.341 seconds, 9.59 MB

Memory Usage

10104480

33 queries logged

  1. SELECT m.*, c.`option` AS component
      FROM www3menu AS m
      LEFT JOIN www3components AS c
      ON m.componentid = c.id
      WHERE m.published = 1
      ORDER BY m.sublevel, m.parent, m.ordering
  2. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
           
      AND jf_content.published=1
       
      AND jf_content.reference_id IN(1,11,20,304,324,262,231,275,340,393,791,661,12,51,348,805,831,13,52,154,795,14,24,53,793,15,797,16,62,803,17,799,68,97,27,387,619,191,221,172,170,76,171,337,418,521,845,175,174,177,237,176,499,511,455,481,523,547,671,184,185,188,423,837,527,179,181,204,235,156,158,159,384,475,675,629,160,161,162,157,192,621,268,270,266,321,264,265,338,416,483,519,843,276,283,278,282,477,677,279,631,280,281,429,277,382,305,306,307,308,424,835,317,330,318,319,320,325,326,327,328,529,341,342,343,345,350,349,408,351,354,745,489,509,356,479,525,549,673,388,400,403,404,405,406,419,513,399,394,396,397,395,617,615,663,665,801,414,163,731,733,735,737,715,739,741,789,743,269,271,272,292,289,290,291,293,294,339,295,420,386,807,811,285,286,288,819,383,287,515,567,809,817,415,284,633,763,315,312,561,563,565,767,314,380,517,332,333,334,335,336,370,346,347,311,378,787,352,364,362,365,833,719,366,367,368,411,412,453,825,379,357,358,359,360,361,371,431,459,463,467,469,471,473,531,533,537,539,541,543,545,599,609,601,605,485,487,491,493,495,497,551,553,557,559,841,573,575,577,579,581,583,585,591,589,777,779,813,749,751,753,755,747,757,759,761,783,373,374,375,376,721,417,829,669,353,413,461,535,781,727,667,611,597,603,815,769,635,637,639,641,645,643,647,649,651,653,655,657,659,785,821,823,827,697,701,703,705,707,709,711)
       
      AND jf_content.reference_table='menu'
  3. SELECT *
      FROM www3rokcandy
      WHERE published=1
  4. SELECT template
      FROM www3templates_menu
      WHERE client_id = 0
      AND (menuid = 0 OR menuid = 406)
      ORDER BY menuid DESC
      LIMIT 0, 1
  5. SELECT *
      FROM www3fsf_settings
  6. SELECT *
      FROM www3fsf_settings_big
  7. SELECT *
      FROM www3fsf_settings_view
  8. SELECT *
      FROM www3fsf_faq_cat
      WHERE published = 1
      ORDER BY ordering
  9. SELECT *
      FROM www3fsf_user
      WHERE user_id = '0'
  10. SELECT id, link
      FROM www3menu
      WHERE link LIKE '%option=com_fsf%'
      AND published = 1
  11. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
           
      AND jf_content.published=1
       
      AND jf_content.reference_id IN(400,388,404,393,394,395,396,397,399,403,405,406,419,513)
       
      AND jf_content.reference_table='menu'
  12. SELECT *
      FROM www3fsf_faq_faq
      WHERE faq_cat_id = '6'
      AND published = 1
      ORDER BY ordering
  13. SELECT *
      FROM www3fsf_faq_faq
      WHERE faq_cat_id = '6'
      AND published = 1
      ORDER BY ordering
      LIMIT 0, 15
  14. SELECT *
      FROM www3fsf_faq_tags
      WHERE faq_id IN (46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60)
      GROUP BY tag
      ORDER BY tag
  15. SELECT COUNT(*) AS cnt
      FROM www3fsf_faq_tags
  16. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  17. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  18. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  19. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  20. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  21. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  22. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  23. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  24. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  25. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  26. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  27. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  28. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  29. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  30. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  31. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  32. SELECT id, title, module, POSITION, content, showtitle, control, params
      FROM www3modules AS m
      LEFT JOIN www3modules_menu AS mm
      ON mm.moduleid = m.id
      WHERE m.published = 1
      AND m.access <= 0
      AND m.client_id = 0
      AND ( mm.menuid = 406 OR mm.menuid = 0 )
      ORDER BY POSITION, ordering
  33. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
           
      AND jf_content.published=1
       
      AND jf_content.reference_id IN(79,330,35,326,331,347,345,329,319,292,335)
       
      AND jf_content.reference_table='modules'

Language Files Loaded

Untranslated Strings Diagnostic

None

Untranslated Strings Designer

None